Mac, running Qt in debug mode always drops me into assembler code?

[st2000]

Hi...

I have been developing an application on a PC for months now. From time to time I try to also build it on a Mac. There are annoying differences (see this thread http://developer.qt.nokia.com/forums/viewthread/9213/ ) which I still need to work on. But lately the Mac version of the application starts up and crashes after only a few seconds. So, I thought I would run it in debug mode and find out what line of C code is causing the problem. But no matter what I do I end up in assembler code. In the call tree I can see what I believe are some of my method names. But clicking on these (backing up) only results in more assembler code. Do I have something set up wrong on the Mac Qt SDK?

-thanks

EDIT: fixed the link, Gerolf

[Franzk]

This suggests the necessary debugging symbols aren't available in the code that crashes. Did you inspect the call stack? Make sure you actually have a debug build and that the libraries you use are debuggable if you need them to be.

[st2000]

bq. Did you inspect the call stack?

Yes, I was looking for my methods (not Qt's) to click on. I believe they were at the top of the call stack (bottom of the window). What confused me is when I clicked on them I didn't see my C-code. Keep in mind this is the same set of files I run on a Windows Qt box. And everything there is working fine.

bq. Make sure you actually have a debug build

I thought clicking on the Qt green arrow with a bug on it was all I had to do. In the old days, I would build with label information (carry coal up hill both ways, ect...). But now I'm at the mercy of the GUI programmer. Where, pray tell, did he/she hide this magic in the Qt GUI?

---

You know, now that I think of it, this may be the results of trying to call phonon at the start of the Qt application.

• Tell me, how well does phonon work on the Mac?

• Is it something that needs to be installed independently of Qt?

• If not installed properly, will Qt act as described here?

...thanks

[Franzk]

[quote author="st2000" date="1316176984"]I thought clicking on the Qt green arrow with a bug on it was all I had to do. In the old days, I would build with label information (carry coal up hill both ways, ect...). But now I'm at the mercy of the GUI programmer. Where, pray tell, did he/she hide this magic in the Qt GUI?[/quote]That doesn't guarantee debug info to be present. You'll have to make sure you have a build type that has debug info present (on gcc the -g option would have to be present etc). Most of that should be available in the Projects window. I'm not familiar with building on mac, so I can't help you further if you'd go into mac specific compilers.

[quote author="st2000" date="1316176984"]- Tell me, how well does phonon work on the Mac? [/quote]
No clue. However, if Phonon is included in the Qt distribution for mac, one would expect it to work at least as well as on windows (daren't say linux here :P. I know how well it works on win and it's good enough to be playing videos with, but don't ask for anything special).

[quote author="st2000" date="1316176984"]- Is it something that needs to be installed independently of Qt?[/quote]Not that I know of. It can be installed separately though. On Linux there are the kde and qt flavours.

[quote author="st2000" date="1316176984"]- If not installed properly, will Qt act as described here?[/quote] If not installed, you wouldn't be able to build the project.

[maherali]

I got this problem few days ago
What I did is just choose the Debug version and clean the project then build it again.
Without cleaning the project I got what you said assembly code.

I hope you can try it and notify us