Xcode 2.1 debugger does not know many types
by Anthony Lovell · in Torque Game Engine · 10/15/2005 (11:17 am) · 2 replies
Is anyone having issues where Xcode seems puzzled by such basics as U32 and almost any (all?) C++ object pointers ("this")? Debugging is really not very powerful when you cannot inspect the data members of the object being debugged owing to an for "this".
tone
tone
#2
You'd add -gfull in the textarea in the bottom of the GCC compiler settings window (select that on left side of panel).
I cannot say that I have any experience with what effect, if any, this has.
tone
10/26/2005 (10:55 am)
For the benefit of others (as I find this a place where XCode is extremely difficult to learn), this setting is NOT under Project->edit project settings, but under Project->Edit target settings.You'd add -gfull in the textarea in the bottom of the GCC compiler settings window (select that on left side of panel).
I cannot say that I have any experience with what effect, if any, this has.
tone
Torque Owner Paul Scott
Default Studio Name
This is a known issue in Apple's recent dev tools. Somehow, gcc is putting out mangled debugging info. There has been much talk of this on the apple mailing lists.
One possible workaround seems to be to change the level of debug symbols generated to -gfull . The default is -gused , which tries to intelligently figure out which bits of code actually need to have debug symbols generated... which may perhaps be the cause. The Apple engineers are working on the issue.
Adding -gfull to the compiler flags seems to help, but does not erradicate the issue completely.