[Qt-interest] Debugging Crash on Windows
Josiah Bryan
jbryan at productiveconcepts.com
Mon Feb 22 23:50:30 CET 2010
Josiah Bryan wrote:
> 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.)
>
Alright, to followup on my own post, I've isolated the crash to a
seemingly innocent line of code:
m_player = new Phonon::VideoPlayer(Phonon::VideoCategory, 0);
(m_player is the proper type)
I've tried setting a breakpoint on that line and stepping into it - but
when I step into it with F11 in the qt creator debugger (qt 4.6.1), it
just keeps showing 'operator new' on the stack, and stopping there.
Repeated presses of F11 result in 'operator new' staying on top the
stack and no change in program position. Pressing F10 (step out) results
in program execution halting with the same message ("The inferior has
stopped because...SIGSEGV").
Any leads on how to get to the bottom of this crash? (OS is Windows XP Pro)
Thanks!
-josiah
More information about the Qt-interest-old
mailing list