[Qt-creator] Debugging Problem (CDB) With Breakpoints In Slots
Thomas Dähling
t.daehling at googlemail.com
Mon Jun 29 15:59:19 CEST 2009
Just out of curiousity: Have you checked that your slot function is
actually supposed to be called, e.g. the signal that slot is connected
to gets emitted and the connect call did not fail?
2009/6/29 Markus Klama <markus at hamilton-engineering.com>:
> I have started using Qt Creator since there is support now for the
> Microsoft CDB debugger. I have encountered a problem with debugging and
> I don't know if this is a bug or a problem related to myself being a
> "Creator Newbie"...
>
> Ok, here's my setup:
> Windows XP 32-bit Professional Service Pack 3
> Microsoft Visual Toolkit 2003 Optimizing Compiler
> Microsoft Debugging Tools 6.11.1.404
> Qt 4.5.2 compiled as a shared library (debug & release)
> Qt Creator 1.2.0
>
> I created a project in Qt Creator, set my build mode to debug, setup the
> path to the CDB Tools.
> Verified that breakpoints are working by setting breakpoints in my
> main.cpp and also in the constructor of my mainwindow class. Everything
> works as expected. Execution stops and the source code window shows me
> where I am. So far, so good.
> Tried to set a breakpoint in a private slot function. Debugger did not
> stop (as if the breakpoint would be disabled).
> Forced a breakpoint at the same position in the slot funtion by
> including windows.h and inserting a DebugBreak() in the source code.
> Debugger did stop and showed the correct source code.
>
> So what am I doing wrong? Why do the breakpoints in mt slots do not
> work? I can work around it using the DebugBreak() method, but that's not
> the way it's supposed to be ....
>
> Thanks,
> Markus
> _______________________________________________
> Qt-creator mailing list
> Qt-creator at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-creator
>
More information about the Qt-creator-old
mailing list