kismet crashes on exit

Bug #216708 reported by Thomas Butter
This bug report is a duplicate of:  Bug #179233: kismet crashed with SIGSEGV in feof(). Edit Remove
4
Affects Status Importance Assigned to Milestone
kismet (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: kismet

after quitting kismet it segfaults.

this is the console log:

# kismet
Launching kismet_server: //usr/bin/kismet_server
Suid priv-dropping disabled. This may not be secure.
No specific sources given to be enabled, all will be enabled.
Non-RFMon VAPs will be destroyed on multi-vap interfaces (ie, madwifi-ng)
Enabling channel hopping.
Enabling channel splitting.
Source 0 (ipw2200): Enabling monitor mode for ipw2200 source interface eth1 channel 6...
Source 0 (ipw2200): Opening ipw2200 source interface eth1...
Will attempt to put networkmanager to sleep...
Allowing clients to fetch WEP keys.
WARNING: Disabling GPS logging.
Logging networks to /var/log/kismet/Kismet-Apr-13-2008-5.network
Logging networks in CSV format to /var/log/kismet/Kismet-Apr-13-2008-5.csv
Logging networks in XML format to /var/log/kismet/Kismet-Apr-13-2008-5.xml
Logging cryptographically weak packets to /var/log/kismet/Kismet-Apr-13-2008-5.weak
Logging cisco product information to /var/log/kismet/Kismet-Apr-13-2008-5.cisco
Logging data to /var/log/kismet/Kismet-Apr-13-2008-5.dump
Writing data files to disk every 300 seconds.
Mangling encrypted and fuzzy data packets.
Tracking probe responses and associating probe networks.
Reading AP manufacturer data and defaults from //etc/kismet/ap_manuf
Reading client manufacturer data and defaults from //etc/kismet/client_manuf
Using network-classifier based data encryption detection
Not tracking duplicate IVs
Putting networkmanager to sleep...
Dump file format: wiretap (local code) dump
Crypt file format: airsnort (weak packet) dump
Kismet 2007.10.R1 (Kismet)
Logging data networks CSV XML weak cisco
Listening on port 2501.
Allowing connections from 127.0.0.1/255.255.255.255
Registering builtin client/server protocols...
Registering requested alerts...
Registering builtin timer events...
Gathering packets...
Launching kismet_client: //usr/bin/kismet_client
Launched client, pid 28757
Looking for startup info from localhost:2501..... found.
Connected to Kismet server 2007.10.R1 on localhost:2501
Reading AP manufacturer data and defaults from //etc/kismet/ap_manuf
Reading client manufacturer data and defaults from //etc/kismet/client_manuf
Segmentation fault (core dumped)

ProblemType: Crash
Architecture: i386
Date: Sun Apr 13 11:57:25 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/kismet
Package: kismet 2007-10-R1-2build1
PackageArchitecture: i386
ProcCmdline: kismet
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=de_DE.UTF-8
Signal: 11
SourcePackage: kismet
Stacktrace:
 #0 0xb7d63b31 in feof () from /lib/tls/i686/cmov/libc.so.6
 #1 0x08049224 in ?? ()
 #2 0x08049cd6 in ?? ()
 #3 0xb7d18450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #4 0x08048e81 in ?? ()
StacktraceTop:
 feof () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Title: kismet crashed with SIGSEGV in feof()
Uname: Linux 2.6.24-16-generic i686
UserGroups:

Tags: apport-crash
Revision history for this message
Thomas Butter (tbutter) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:feof () from /lib/tls/i686/cmov/libc.so.6
reap (sig=0) at kismet_wrapper.cc:81
main (argc=1, argv=0xbf8d6984, envp=) at kismet_wrapper.cc:311

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in kismet:
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.