Gdb stops at "setting breakpoints" in QtCreator when debugging
-
wrote on 19 Dec 2010, 23:08 last edited by
Now it suddenly works, without me doing any changes! This is very strange...
This is the log for it: http://pastebin.com/yXQw4DJL
and the left split: http://pastebin.com/Rb5j5wS9 -
wrote on 19 Dec 2010, 23:38 last edited by
I'd say the behaviour is quite strange and erratic. If I stop at a breakpoint, the program crashes or gets locked up (for instance within a setScene or addText), but if I remove all breakpoints, it works.
It behaves like it's very timing dependent, and one breakpoint in the beginning brakes it. The annoying thing is of course that it shouldn't be timing dependent, it's just a simple application with only one thread. -
wrote on 1 Jan 2011, 10:14 last edited by
Hello? Anyone? This is still an issue...
-
wrote on 1 Jan 2011, 17:58 last edited by
It's holiday time ... please wait for another couple of days.
-
wrote on 7 Jan 2011, 17:09 last edited by
Hello,
I have the same problem...
I'm new on my fedora14 plateform and with Qt Creator 2.0.1 based on Qt 4.7.0 (64bits) and Gdb (7.2) I have this message in debug:&"warning: GDB: Failed to set controlling terminal: Argument invalide\n"
and it not stop on my breaksPoints... :S
Any idea to solve this problem?
thx
jerome
-
wrote on 8 Jan 2011, 10:33 last edited by
The "controlling terminal" message can be ignored... nobody seems to know why gdb fails there (incl. the gdb developers):-(
From my experience most developers do not follow any forum. Bugreports and mailing lists are their way of communication. So please file a "bug report":http://bugreports.qt.nokia.com/ if you want to make sure the developers will be notified about the issue.
-
wrote on 18 Jan 2011, 18:40 last edited by
Thanks, I was looking for a place to do that! I did however think that the devs followed the official forum.
-
wrote on 21 Jan 2011, 09:33 last edited by
I've posted a bug about it, and I have received an answer as well. Seems like it's fixed in the 2.1 branch, so either you can try to apply the patch yourself (it's mentioned in the bug) or wait for the new release. Let's cross our fingers and hope it works!
http://bugreports.qt.nokia.com/browse/QTCREATORBUG-3534?focusedCommentId=138529#comment-138529
-
wrote on 21 Jan 2011, 11:31 last edited by
Glad you got your issue fixed:-)
-
wrote on 27 Feb 2014, 11:17 last edited by
I moved to Linux in 2014, and I'm facing the same issue. (on Windows it worked nice)
Linux Mint 13 (Ubuntu 12.04 derivative), Qt Creator 3.0.1, Qt 5.2.1, gdb 7.4-2012.04. Behavior exactly the same: stuck on 'Setting breakpoints...', and after 40 seconds the message:
The gdb process has not responded to a command within 40 second(s). This could mean it is stuck in an endless loop or taking longer than expected to perform the operation. You can choose between waiting longer or aborting debugging.
I tried to install latest gdb 7.7, I have set my Qt project to use it, but nothing is changed.
How to solve it now?
-
wrote on 27 Feb 2014, 12:33 last edited by
It's strange that this old bug would resurface... Perhaps it's a regression in QtCreator. I haven't used it in a while, so I haven't seen if the bug has come back.
On another note, I would really recommend you to update to the latest version of Mint (if you're familiar with that and prefer it) since all dependencies are vastly updated on a modern version. Isn't it possible to do an upgrade to a newer version? Instead of a clean install I mean.
-
wrote on 28 Feb 2014, 08:07 last edited by
Thanks for the suggestion but I really want to stick to LTS release, so updating Mint is not an option for me.
-
wrote on 28 Feb 2014, 08:48 last edited by
LTS is overrated :) But I digress!
Perhaps you should either re-enable the bug to see if they can help you, or file a new bug and link to my old one.
Good luck!