[Qt-interest] Debugging Crash on Windows

Thiago Macieira thiago at kde.org
Tue Feb 23 08:31:43 CET 2010


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.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
Url : http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20100223/46579581/attachment.bin 


More information about the Qt-interest-old mailing list