[Qt-interest] TimerIds Destructor crashes when exiting application

[Srdjan Todorovic]

Hi,

On 11/08/2009, Marc Ferland <ferlandm at sonatest.com> wrote:
> Hi all,
>
> I'm having a really weird problem when I close my application and it
> seems to be related to timers. Here's the stack when the application
> is crashing:
>
> #0  0x00007f27c12d8ed5 in raise () from /lib/libc.so.6
> #1  0x00007f27c12da3f3 in abort () from /lib/libc.so.6
> #2  0x00007f27c13153a8 in ?? () from /lib/libc.so.6
> #3  0x00007f27c131a948 in ?? () from /lib/libc.so.6
> #4  0x00007f27c131ac10 in ?? () from /lib/libc.so.6
> #5  0x00007f27c131c708 in ?? () from /lib/libc.so.6
> #6  0x00007f27c131ca56 in free () from /lib/libc.so.6
> #7  0x00007f27c312c15e in timerIdsDestructorFunction () at
> kernel/qabstracteventdispatcher.cpp:74
> #8  0x00007f27c312c769 in ~timerIdsDestructorFunction__dest_class__
> (this=0x7f27c3479ac0) at kernel/qabstracteventdispatcher.cpp:76
> #9  0x00007f27c12dbd88 in __cxa_finalize () from /lib/libc.so.6
> #10 0x00007f27c3009a86 in __do_global_dtors_aux () from
> /usr/local/Trolltech/Qt-4.5.2/lib/libQtCore.so.4
> #11 0x00000000004a5b90 in ?? ()
> #12 0x00007fffd0f82a60 in ?? ()
> #13 0x00007f27c31a36e1 in _fini () from
> /usr/local/Trolltech/Qt-4.5.2/lib/libQtCore.so.4
> #14 0x0000000000000052 in ?? ()
> #15 0x00007f27c8d75d64 in ?? () from /lib64/ld-linux-x86-64.so.2
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
>
> Any of you seen this before?

It doesn't make sense, since as gdb reports, the stack looks corrupt.
Especially for frame 14.

My gut feeling is that something previous to this is causing the
problem (and in doing so, corrupts the stack frames).

Also note frame 1, where libc's abort() function is called. Is this a
libc-detected abort (double-free) or a plain old segmentation fault?

Srdjan