[Qt-interest] Debugging Crash on Windows
Josiah Bryan
jbryan at productiveconcepts.com
Tue Feb 23 14:14:38 CET 2010
Thiago Macieira wrote:
> Em Terça-feira 23. Fevereiro 2010, às 04.00.13, Josiah Bryan escreveu:
>> william.crocker at analog.com wrote:
>>> Josiah Bryan wrote:
>>>> 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.)
>>> The first lines of defense:
>>>
>>> valgrind
>>> purify($)
>> Valgrind on windows? Hows that work? Googling doesn't show up much info,
>> other than some blogs complaining about lack of windows support...
>
> It's not. On Windows, you can buy Purify and use that.
>
> For Valgrind, it's useful to have a Linux in a VM just to test your
> application. Valgrind alone is reason enough to do so.
Understood. However, the crash only happens on windows. I run Linux as
my primary OS both at home and work. I only really use Windows XP on my
laptop. If it was crashing on linux, I'd probably have it fixed by now,
as gdb on linux is much easier use to troubleshoot crashing as a result
of UI interaction.
-josiah
More information about the Qt-interest-old
mailing list