kismet crashed with SIGSEGV in __kernel_vsyscall()

Bug #454114 reported by Mihai Mustea
This bug report is a duplicate of:  Bug #179233: kismet crashed with SIGSEGV in feof(). Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kismet (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: kismet

ProblemType: Crash
Architecture: i386
Date: Sat Oct 17 19:54:10 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kismet
Package: kismet 2008-05-R1-4ubuntu3
ProcCmdline: kismet
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SegvAnalysis:
 Segfault happened at: 0x18cd81 <feof+33>: cmp %edi,0x8(%edx)
 PC (0x0018cd81) ok
 source "%edi" ok
 destination "0x8(%edx)" (0x00000049) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: kismet
StacktraceTop:
 __kernel_vsyscall ()
 select () 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 __kernel_vsyscall()
Uname: Linux 2.6.31-11-generic i686
UserGroups:

Revision history for this message
Mihai Mustea (mihai-mustea) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:__kernel_vsyscall ()
___newselect_nocancel () from /lib/tls/i686/cmov/libc.so.6
main (argc=1, argv=0xbf8ce3d4, envp=0xbf8ce3dc)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in kismet (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Connor Imes (ckimes)
visibility: private → public
Bob Bib (bobbib)
tags: added: karmic
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.