Yes , the application works , but the debugger doesn't . There is some miscommunication between QtCreator and GDB , because , as I said segfaults get interpreted as a crash on startup , and there's no option to pause the app and ... debug .
On 12/01/2013 07:04 PM, André Pönitz wrote: > On Sun, Dec 01, 2013 at 04:14:24PM +0200, Petko Ditchev wrote: >> Hi guys , I hadn't used QtCreator and Qt in a week or two and now ,after I >> downloaded the RC1, I see that debugging is broken . I tested gdb from the >> command line and it works just fine , but in QtCreator it gets stuck on >> "Setting breakpoints" (or something like that) and there's no way to pause >> the >> application or to detect segfaults (they get reported as a break during >> startup) , while the app itself starts up normally . Here's my debugging >> output >> (I've replaced the project dir path with ~~~) (my system is manjaro): >> >> >> sStarting debugger "GdbEngine" for ABI "x86-linux-generic-elf-64bit"... >> [...] > There is nothing in this log indicating that there's an attempt to set > breakpoints. > > The last bit reads > >> [..] >> dQUEUE: RUN ENGINE >> dCALL: RUN ENGINE >> <250-exec-run >> &"warning: GDB: Failed to set controlling terminal: Inappropriate ioctl for >> device\n" >>> =thread-group-started,id="i1",pid="7465" >> sThread group i1 created >> dTaking notice of pid 7465 >>> =thread-created,id="1",group-id="i1" >> sThread 1 created > so according to the log your application is running normally now. > > Andre' _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
