debugger Mac OS

mrjj

hi and welcome back
maybe this can cast some light
https://forum.qt.io/topic/32743/no-debugger-setup-for-mac-os-x/14
Sorry I can't be more direct, only linux & win here.

aktk

I'm also struggling with OS X debugging at the moment: after updating Xcode to 7.2 debug just doesn't work. Reinstalling of Qt to latest revision doesn't help.

SGaist

Hi,

The debugger options are under Preferences -> Debugger on OS X.

But the first thing to check is whether your Kit is currently using clang and lldb.

Hope it helps

mzimmers

I don't think Qt had "kits" when I was using it. Is this the new name for the tool chains?

And...where do I inspect the details of a kit?

I don't know how to imbed pictures, but here are a couple of snapshots that might help:

scopedin.com/images/debug.jpg
scopedin.com/images/debug2.jpg

Thank you for the help.

SGaist

It's a specific setup for Qt + Compiler + Debugger + mkspecs.

Go to Preferences -> Build and Run

mzimmers

OK, this is what I have. I still can't get it to run.

http://scopedin.com/images/debug3.jpg

SGaist

What do you have in your Kit ?

mzimmers

This:

http://scopedin.com/images/debug4.jpg

SGaist

Looks fine… What error are you getting ?

mzimmers

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.

SGaist

XQuartz ?

Are you also getting this with a default Qt project ?

mzimmers

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?

SGaist

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 ?

mzimmers

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...

SGaist

Sorry, I meant on your project executable

mzimmers

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$

SGaist

So it's not even a Qt based application ?

mzimmers

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.

SGaist

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.

mzimmers

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.