Application doesn't end

[Vadim Zeitlin]

On 28 Dec 2006 10:39:02 -0800 franky.braem at gmail.com wrote:

> 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 ...

 The only other explanation I have is that memory is seriously corrupted by
this time. It's just impossible for a thread to block on a mutex if it's
not owned by another thread (because there are none) otherwise.

 Regards,
VZ

-- 
TT-Solutions: wxWidgets consultancy and technical support
               http://www.tt-solutions.com/