On 3/22/10 8:58 AM, André Pönitz wrote: > On Sunday 21 March 2010 22:13:09 ext Stephen Chu wrote: >> OK. Another mystery (or embarrassment?) here. I tried my project on >> Windows Qt Creator and got the same no debug helper look. I made sure >> the use debug helper option is on and rebuilt the helper. Still no >> format output. Recheck for debugging helper availability resulted in >> "Debugging helpers not found" message. > > This looks like a Qt Creator 2.0-alpha trying to use a gdb 6.8 - which > is (on Windows) an unsupported (and known-to-fail) combination. > > If you don't have a Python-enabled gdb at hand, try to fetch one > from ftp://ftp.qt.nokia.com/misc/gdb/ or install the Qt Creator > package using the binary installer. > > In case you already have a gdb-7.0.1 or such (possibly even installed > using Creator's installer), make sure to point your gdb settings to > this place (and consider filing a bugreport as this was not caught > automatically). >
The Creator 2.0 alpha binary package does install both gdb 6.8 in mingw dir and python gdb in its own dir. The gdb preferences still points to the mingw one since this is a upgrade install. But after I point it to the python one (gdb-i686-pc-mingw32.exe), I now get an error trying to start a debugging session: "Executable failed: During startup program exited with code 0xc0000135." I am starting to this Creator 2 alpha works only with Qt 4.7 now. Really frustrating. :( Filed a bug on this: <http://bugreports.qt.nokia.com/browse/QTCREATORBUG-934> Back to Mac for debugging... -- Stephen Chu <mailto:[email protected]> <http://www.ju-ju.com> _______________________________________________ Qt-creator mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator
