Application doesn't end

franky.braem at gmail.com franky.braem at gmail.com
Thu Dec 28 10:39:02 PST 2006



Vadim Zeitlin schreef:

> On 11 Dec 2006 11:27:32 -0800 franky.braem at gmail.com wrote:
>
> > Finally managed to run a debugger on Ubuntu and I see the following
> > stack when I suspend the application:
> >
> > Thread [1] (Suspended: Signal 'SIGINT' received. Description:
> > Interrupt.)
> > 	12 __kernel_vsyscall()  0xffffe410
> > 	11 __lll_mutex_lock_wait()  0xb7bda2ae
> > 	10 _L_mutex_lock_33()  0xb7bd6fbb
> > 	9 <symbol is not available> 0x0815dc08
> > 	8 <symbol is not available> 0xbfb56e08
> > 	7 free()  0xb7b0434a
> > 	6 wxMutexInternal::Lock()  0x080d2aa7
> > 	5 wxThreadModule::OnExit()  0x080d41e1
> > 	4 wxModule::DoCleanUpModules()  0x080c0021
> > 	3 wxEntryCleanup()  0x080b392f
> > 	2 wxEntry()  0x080b3d2a
> > 	1 main() at /home/bronx/wxJS/src/db/main.cpp:43 0x0806e2fc
>
>  There must be another thread (use "info thr" and "thr" commands) which
> hadn't been terminated probably?

It's been a while before I could test this again. I get this
information (much like above):

(gdb) info threads
* 1 Thread -1213196608 (LWP 4088)  0xffffe410 in __kernel_vsyscall ()
(gdb) thread 1
[Switching to thread 1 (Thread -1213196608 (LWP 4088))]#0  0xffffe410
in __kernel_vsyscall ()
(gdb) info stack
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7c4e2ae in __lll_mutex_lock_wait ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb7c4afbb in _L_mutex_lock_33 () from
/lib/tls/i686/cmov/libpthread.so.0
#3  0x0815ebe8 in ?? ()
#4  0xbfbc9d38 in ?? ()
#5  0xb7b7834a in free () from /lib/tls/i686/cmov/libc.so.6
#6  0x080d3687 in wxMutexInternal::Lock ()
#7  0x080d4dc1 in wxThreadModule::OnExit ()
#8  0x080c0c01 in wxModule::DoCleanUpModules ()
#9  0x080b450f in wxEntryCleanup ()
#10 0x080b490a in wxEntry ()
#11 0x0806e71c in main (argc=1, argv=0xbfbc9e84) at main.cpp:44

So there's only one thread waiting ...







More information about the wx-users mailing list