Unsolved debugger Mac OS
-
-
Looks fine… What error are you getting ?
-
I'm not getting an error, but when I try to start debugging, the debug controls (step over, step into, etc) aren't enabled. The display says the debugger is busy, but it doesn't seem to be doing anything.
This could be cockpit error, as I haven't used Creator in a couple years.
EDIT: when I start the debug session, it opens an XQuartz session as well.
-
XQuartz ?
Are you also getting this with a default Qt project ?
-
I'm not sure I know what you mean by default Qt project, but I tried creating a Qt Console application, and the results are the same.
Perhaps I should remove Qt and reinstall?
-
That's what I meant, or with a widget application but the result would probably be the same.
Can you run
otool -L
on the executable ? -
Mac-Mini:bin mzimmers$ pwd /usr/bin Mac-Mini:bin mzimmers$ otool -L lldb lldb: /usr/lib/libxcselect.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1226.10.1) Mac-Mini:bin mzimmers$
Thanks...
-
Sorry, I meant on your project executable
-
Mac-Mini:build-QtPrime-Desktop_Qt_5_5_1_clang_64bit-Debug mzimmers$ otool -L QtPrime
QtPrime:
/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 120.1.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1226.10.1)
Mac-Mini:build-QtPrime-Desktop_Qt_5_5_1_clang_64bit-Debug mzimmers$ -
So it's not even a Qt based application ?
-
I'm trying to start with something minimal, just to get it working.
I think I may have found the problem, though...the run option "Run In Terminal" was checked by default. I removed that, and I think it's working, though I"m not sure what I'll do if I need to furnish input.
-
Haaaaa, didn't thought about that one… You can check the Environment part in the Preferences to see what terminal it's using. That might explain why XQuartz gets started.
-
Currently, it's set to:
/Developer/Applications/Qt/Qt\ Creator.app/Contents/MacOS/../Resources/scripts/openTerminal.command
And, as I suspected, cin doesn't work.
-
I don't know if it can be considered a bug… I haven't used the Terminal for debugging for a long time.
-
OK, so let's say I wanted to create a "hello world" project that accepts an integer and prints "hello world" that many times...which project template should I use for this?
-
Non-Qt project -> Plain C or Plain C++ application
-
I must not be asking the question the right way...I began by using a non-Qt project. That's when it popped up Xterm on me.
What do I need to do, to get the debugger to accept character-based input?
Thanks.
-
Ok sorry, I get it now.
The thing is, it should work but there's something that seems to start maybe Xterm rather than Terminal. What happens if you call
/Applications/Qt\ Creator.app/Contents/MacOS/../Resources/scripts/openTerminal.command
from your terminal ? -
I don't have anything in that path. My installation is in /Developer/Applications.
If I run:
/Developer/Applications/Qt/Qt\ Creator.app/Contents/MacOS/../Resources/scripts/openTerminal.command
Then I get a new terminal window, but it's under control of the shell, not my app.