[Qt-interest] Debugging Crash on Windows

[Josiah Bryan]

Hey All -

I'm trying to debug a phonon-related program crash using the debugger in 
Qt Creator. However, when I click the button that causes the crash, the 
debugger exits with a totally unrelated stack trace (below.)

I even installed my own message handler using qInstallMsgHandler trying 
to catch QtFatalMsg and set a breakpoint in that code to catch the 
stacktrace that way - well, it never even hits that breakpoint.

The popup box that appears from Qt Creator says: "The inferior has 
stopped because it received a signal from the Operating System", and 
says the sig was SIGSEGV. That's fine - the stack trace indicates some 
internal problem in QListData. But look at where the stack trace starts 
- its when the program is exiting. The program was never told to exit 
though - it was supposed to play a video upon clicking the button - but 
instead the debugger halts with the SIGSEGV msg and the following stack 
trace:

0    QListData::size    qlist.h    90    0x06f24336   
1    QList<void (*)(QPixmap*)>::count    qlist.h    261    0x06f15a75   
2    QImagePixmapCleanupHooks::executePixmapDestructionHooks    
qimagepixmapcleanuphooks.cpp    109    0x06869390   
3    ~QPixmap    qpixmap.cpp    324    0x0685a955   
4    ~QPixmapCacheEntry    qpixmapcache.cpp    435    0x0685f27b   
5    QCache<QPixmapCache::Key, QPixmapCacheEntry>::clear    qcache.h    
139    0x06ea2670   
6    QPMCache::clear    qpixmapcache.cpp    415    0x0685ef80   
7    ~QPMCache    qpixmapcache.cpp    224    0x0685e4f8   
8    ~QGlobalStaticDeleter    qglobal.h    1799    0x06e2bb6f   
9    __tcf_0    qpixmapcache.cpp    425    0x0685effc   
10    __dll_exit    C:\j\EW-Data\dviz-qt4.6-rc1\src\debug\QtGuid4.dll    
0    0x067a102f   
11    DllMainCRTStartup at 12    
C:\j\EW-Data\dviz-qt4.6-rc1\src\debug\QtGuid4.dll    0    0x067a10f5   
12    ntdll!LdrSetAppCompatDllRedirectionCallback    
C:\WINDOWS\system32\ntdll.dll    0    0x7c90118a   
13    ??        0    0x067a0000   
14    ??        0    0x00000000   

Any ideas?
Thanks!
-josiah