[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug-gnubg] multithread closing bug
From: |
Christian Anthon |
Subject: |
[Bug-gnubg] multithread closing bug |
Date: |
Fri, 4 May 2007 23:06:58 +0200 |
Hi Jon and others,
most of the time when I close the mt version I get the following error on exit
GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Device or
resource busy' during 'pthread_mutex_destroy ((pthread_mutex_t *)
mutex)'
aborting...
with the corresponding back-trace
#0 0x0091a402 in __kernel_vsyscall ()
#1 0x437a9f30 in raise () from /lib/libc.so.6
#2 0x437ab781 in abort () from /lib/libc.so.6
#3 0x43951f6a in g_logv () from /lib/libglib-2.0.so.0
#4 0x43951fa9 in g_log () from /lib/libglib-2.0.so.0
#5 0x442501da in ?? () from /lib/libgthread-2.0.so.0
#6 0x080f725d in FreeMutex (mutex=0xcd6f8b8) at multithread.c:155
#7 0x080f7e2f in MT_Close () at multithread.c:521
#8 0x0806c536 in Shutdown () at gnubg.c:3749
#9 0x08075e33 in main (argc=1, argv=0xbfce2654) at gnubg.c:6847
It is as far as I can tell always the line (521)
FreeMutex(td.queueLock);
that causes the problem. A g_usleep(1000) (that is 1ms) added just
after MT_CloseThreads, seems to cure the problem.
Not a very serious problem obviously, but it might be an indication of
a more fundamental problem.
Christian.
always
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug-gnubg] multithread closing bug,
Christian Anthon <=