On 10/22/2010 05:19 PM, Andre Poenitz wrote: > > Hi Abdel ;-) > > On Fri, Oct 22, 2010 at 04:27:35PM +0200, Abdelrazak Younes wrote: >> Hello, >> >> Lately (and suddenly), either with self-compiled latest git or with >> QtCreator-2.1beta I can not debug within QtCreator anymore. Debugging >> with straight gdb at the command line works fine. Here is the issue: >> >> * If there's no breakpoint in my application, pressing F5 works fine, no >> crash at all. >> >> * If I put a breakpoint somewhere, QtCreator will correctly stop but >> once I reach a line of code using QString or QByteArray, my program >> crashes with the following dialog: >> >> "The inferior stropped because it received a signal from the Operation >> System. >> Signal name: 0 >> Signal meaning: 0" > > This is a bogus signal send/created by gdb itself IIRC. At least there > is no valid system signal 0.
Forgot to say: GNU gdb (GDB) 7.0.50.20100120-cvs gcc version 4.4.5 > I think Qt Creator should ignore it (or > perhaps as a normal "stop") not handle it as a termination indication. Well gdb itself seems to hapily ignore it as it doesn't stop. Abdel. _______________________________________________ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
