[Qt-interest] Segfault with a qapplication running in a boost::thread

[Damien R]

Damien R wrote:
> The app crashes after about 1h with the current backtrace :
> #0  0xb7f35430 in __kernel_vsyscall ()
> #1  0xb7bd16d0 in raise () from /lib/tls/i686/cmov/libc.so.6
> #2  0xb7bd3098 in abort () from /lib/tls/i686/cmov/libc.so.6
> #3  0xb7c0f24d in ?? () from /lib/tls/i686/cmov/libc.so.6
> #4  0xb7c15604 in ?? () from /lib/tls/i686/cmov/libc.so.6
> #5  0xb7c185b6 in ?? () from /lib/tls/i686/cmov/libc.so.6
> #6  0xb7c18fbf in ?? () from /lib/tls/i686/cmov/libc.so.6
> #7  0xb7c19ee6 in realloc () from /lib/tls/i686/cmov/libc.so.6
> #8  0xb6f8c064 in qRealloc (ptr=0xa235e98, size=32) at global/qmalloc.cpp:65
> #9  0xb6fb6d25 in QListData::realloc (this=0xb5af0074, alloc=3) at
> tools/qlistdata.cpp:111
> ....
> #36 0xb708406a in QEventLoop::processEvents (this=0xb5af1290, flags={i
> = -1246817704}) at kernel/qeventloop.cpp:149
> #37 0xb70844aa in QEventLoop::exec (this=0xb5af1290, flags={i =
> -1246817640}) at kernel/qeventloop.cpp:200
> 
> I am suspicious about the stackframe #37 when the backtrace shows
> flags={i = -1246817640}.
> So, is it a dangling pointer which corrupt the flags, or something else ?

The problem was due to the fact I did not use signal/slot or mutex to 
restart a QTimer and clear a QLabel. Now the app works fine.

--
Damien R.