You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Uncaught exception "basic_string::substr: __pos (which is 3) > this->size() (which is 1)"
Stack trace (most recent call last) in thread 65216: #8 Object ", at 0xffffffffffffffff, in #7 Source "../sysdeps/unix/sysv/linux/x86_64/clone3.S", line 78, in clone3 #6 Source "./nptl/pthread_create.c", line 444, in start_thread #5 Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.32, at 0x7f061ece6332, in #4 Object "/usr/bin/kismet, at 0x560ed70aa41a, in #3 Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.32, at 0x7f061ecb6e5d, in std::rethrow_exception(std::__exception_ptr::exception_ptr) #2 Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.32, at 0x7f061ecb6ed6, in std::terminate() #1 Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.32, at 0x7f061ecb6e6b, in
#0 Object "/usr/bin/kismet, at 0x560ed70a78d4, in TerminationHandler()
Uncaught exception "std::exception"
FATAL: Encountered an error receiving data from Kismet Kismet connection lost
Aborted
The text was updated successfully, but these errors were encountered:
I'll keep an eye out for it, but unfortunately there's no info there to make any guesses. If you're able to get it to happen repeatedly, please try the debug instructions from the docs:
https://kismetwireless.net/docs/dev/debugging/
also if you can try w/ the latest git code (or nightly builds), so much has changed since the last release it may have been fixed some time ago if it was something that was reproducible.
On Saturday, March 2nd, 2024 at 7:08 PM, Peter Nearing ***@***.***> wrote:
kismet --version
Kismet 2023-07-R1
Ubuntu Mantic (23.10) Amd64.
Uncaught exception "basic_string::substr: __pos (which is 3) > this->size() (which is 1)"
Stack trace (most recent call last) in thread 65216:
[#8](#8) Object ", at 0xffffffffffffffff, in
[#7](#7) Source "../sysdeps/unix/sysv/linux/x86_64/clone3.S", line 78, in clone3
[#6](#6) Source "./nptl/pthread_create.c", line 444, in start_thread
[#5](#5) Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.32, at 0x7f061ece6332, in
[#4](#4) Object "/usr/bin/kismet, at 0x560ed70aa41a, in
[#3](#3) Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.32, at 0x7f061ecb6e5d, in std::rethrow_exception(std::__exception_ptr::exception_ptr)
[#2](#2) Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.32, at 0x7f061ecb6ed6, in std::terminate()
[#1](#1) Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.32, at 0x7f061ecb6e6b, in
#0 Object "/usr/bin/kismet, at 0x560ed70a78d4, in TerminationHandler()
Uncaught exception "std::exception"
FATAL: Encountered an error receiving data from Kismet Kismet connection lost
Aborted
—
Reply to this email directly, [view it on GitHub](#511), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AFKJYY7AASS7ZBARWPMWAPLYWJSY3AVCNFSM6AAAAABEDPDCP2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGE3DKMBTHEYDMNY).
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
kismet --version
Kismet 2023-07-R1
Ubuntu Mantic (23.10) Amd64.
Uncaught exception "basic_string::substr: __pos (which is 3) > this->size() (which is 1)"
Stack trace (most recent call last) in thread 65216:
#8 Object ", at 0xffffffffffffffff, in
#7 Source "../sysdeps/unix/sysv/linux/x86_64/clone3.S", line 78, in clone3
#6 Source "./nptl/pthread_create.c", line 444, in start_thread
#5 Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.32, at 0x7f061ece6332, in
#4 Object "/usr/bin/kismet, at 0x560ed70aa41a, in
#3 Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.32, at 0x7f061ecb6e5d, in std::rethrow_exception(std::__exception_ptr::exception_ptr)
#2 Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.32, at 0x7f061ecb6ed6, in std::terminate()
#1 Object "/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.32, at 0x7f061ecb6e6b, in
#0 Object "/usr/bin/kismet, at 0x560ed70a78d4, in TerminationHandler()
Uncaught exception "std::exception"
FATAL: Encountered an error receiving data from Kismet Kismet connection lost
Aborted
The text was updated successfully, but these errors were encountered: