[Qt-creator] Debugging in QtCreator only shows disassembly

Ziller Eike Eike.Ziller at theqtcompany.com
Thu Nov 5 08:57:45 CET 2015

> On Nov 4, 2015, at 8:21 PM, Steve Atkins <steve at blighty.com> wrote:
>> On Nov 4, 2015, at 11:11 AM, israel at eraalaska.net wrote:
>> It would appear that the problem lies with running the macdeployqt script after build. If I don't run it, then I can debug my app - except that my app needs to be sandboxed, and if I sandbox the app but DON'T run macdeployqt, then the app crashes - probably because it doesn't have read access to the Qt libraries. Without sandboxing, I get weird behavior (specifically, it appears to be getting some settings from SOMEWHERE - using QSettings -, but for the life of me I can't figure out where), and it's not really a valid test anyway. So I'm a bit stumped here - unless I can somehow modify macdeployqt to prevent breaking debugging?
> macdeployqt --help says:
>   -no-strip          : Don't run 'strip' on the binaries
>   -use-debug-libs    : Deploy with debug versions of frameworks and plugins (implies -no-strip)

And/or running dsymutil on your executable before macdeployqt, to save the debug info, might help too.

Eike Ziller, Senior Software Engineer - The Qt Company GmbH
The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B

More information about the Qt-creator mailing list