Ubuntu
swscanner package

SWScanner crashes with SIGSEGV

Bug #110207 reported by Pete Cousen
This bug report is a duplicate of:  Bug #109753: [Lucid] SWScanner crashes. Edit Remove
4
Affects Status Importance Assigned to Milestone
swscanner (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: swscanner

Kernel 2.6.20-15.27

TI ACX111 wlan interface

Crashes with following backtrace

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232218416 (LWP 9050)]
[New Thread -1237300336 (LWP 9089)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb7072cb8 in ?? () from /usr/lib/libqt-mt.so.3
#0 0xb7072cb8 in ?? () from /usr/lib/libqt-mt.so.3
#1 0xb70ae850 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#2 0xb7122136 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#3 0xb7121f46 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#4 0xb7109609 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#5 0x0805b502 in ?? ()
#6 0x080c07a8 in ?? ()
#7 0x080fd248 in ?? ()
#8 0x00000001 in ?? ()
#9 0x00000000 in ?? ()

Revision history for this message
ndege (lpjl) wrote :

I am receiving the same crash on Ubuntu 7.04 Feisty. Running on a Toshiba Tecra M2 with the Intel Centrino / Intel PRO/Wireless 2200BG wifi; using the included ipw2200 network driver (2200/2915) v1.2.0kmprq driver (as reported by dmesg) which was autodetected/supplied by ubuntu. This was originally a dapper install. Under dapper, swscanner worked great. Now I receive the same SIGSEGV crash. Any ideas?

Revision history for this message
ndege (lpjl) wrote :

Additionally, I have been using this under edgy for the past few months...with great success. Kernel 2.6.20-15.27-386.

Revision history for this message
ndege (lpjl) wrote :

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232595248 (LWP 8354)]
[New Thread -1237509232 (LWP 8411)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb6932ec6 in gettimeofday () from /lib/tls/i686/cmov/libc.so.6
#2 0xb709dec8 in ?? () from /usr/lib/libqt-mt.so.3
#3 0xbfc779a0 in ?? ()
#4 0x00000000 in ?? ()

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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