[Qt-interest] Debugging for QT

[Sean Harmer]

Hi,

On Monday 16 May 2011 17:39:26 yogesh upreti wrote:
> Thanks a lot guys.
> My problem was not the meaning of these warning messages.
> It was not clear that where these were coming from.
> 
> I took the old exit/printf statement approach to find out the but, took me 2
> hours but I was able to find it out.
> 
> I am still not clear as in how to work with debugger. It gives me lot of
> "Dump messages" but no file names, and in all the tutorials from QtCreator
> shows a nice "backtrace" to problem areas.
> 
> I hope I don't have to use it anymore. :)

With this kind of error I find the quickest way is to run the app in the 
debugger with the environment variable QT_FATAL_WARNINGS=1 set. When Qt throws 
that assertionm, the debugger will catch it and break. You can then just click 
back up the call stack to see where in your code is triggering the error.

Cheers,

Sean