Re: Debugger can't find correct source file
Re: Debugger can't find correct source file
- Subject: Re: Debugger can't find correct source file
- From: Jim Ingham <email@hidden>
- Date: Tue, 31 Jan 2006 11:00:24 -0800
Not really, sorry... If the breakage is coming about because of code
getting inlined, you could see if -fno-inline helps. You wouldn't
want to do that with a development build, but it may be okay for a
debug build. There doesn't seem to be an Xcode way to do this, but
you can just add the flag to the "Other C Flags".
Jim
On Jan 31, 2006, at 8:35 AM, Jason Bobier wrote:
Thanx for the explanation Jim. Would you happen to have any other
suggestions for how to get around this bug?
Jason
--
Jason Bobier email@hidden
PGP Corporation
www.pgp.com
On Jan 30, 2006, at 10:26 AM, Jim Ingham wrote:
On Jan 29, 2006, at 8:19 PM, Jason Bobier wrote:
Hey Jeremy,
I filed a bug report with a bunch of info from a debug run that
demonstrated this. I haven't heard anything back yet tho.
The linker mauled the debug info - in particular it removed the
marker that tells the debugger that the source file switched back
from an header file to the main source file. Your bug is sitting
with cc tools. This usually happens when the linker has to
coalesce functions among various .o files - for instance resolve
multiple instances of methods defined in header files down to one
copy. Sometimes it removes bits of the debug information along
with the stuff it should remove. For reasons that are not quite
clear yet, this seems to be happening more frequently of late.
As a possible work around, I find that sometimes if I shuffle the
link order of the files around I can sometimes debug into a
function that I couldn't before.
Yeah, you probably made the copy that was getting stripped (and
thus corrupting the debug info) into the "winning" copy, so it
doesn't get stripped...
Jim
Jason
--
Jason Bobier email@hidden
Space Cowboy http://www.prismatix.com/
It's hard to pull yourself up by your bootstraps if your feet are
bare.
On Jan 29, 2006, at 11:09 AM, Jeremy Sagan wrote:
Apparently this is not just a objective C or framework problem
as it happens in my pure C code as well. I step into the
function and instead of opening the source file it opens
memory.h or some other inappropriate source file. This is on an
intel iMac with 10.4.4. Xcode 2.2.1
Is this a known bug?
Jeremy
On Jan 10, 2006, at 1:48 PM, Jason Bobier wrote:
No takers on this eh?
BTW, this happens regardless of whether I attempt to debug from
the app's project or the from the framework's project (setting
the app up as the executable).
Also, I'm building into a common build directory.
Thanx for any help!
Jason
--
Jason Bobier email@hidden
PGP Corporation
www.pgp.com
On Jan 9, 2006, at 12:08 PM, Jason Bobier wrote:
Hey all,
I'm having problems with the debugger in XCode refusing to
show the correct source file when I step into a framework. The
source is a .mm file containing the method definitions of a C+
+ class. Instead it shows the declaration of a parent class in
a header file. The Variable pane correctly shows the variables
for the method that it should be stepping through however, so
I know the debugging info is there. And when I step, it steps
correctly as if the correct source file was being shown (i.e.
the pointer moves the correct number of lines) but continues
to display the wrong file.
Is this a known issue with objective-c++ debugging? Is there a
way to tell xcode which source file I want to display? I seem
to remember some gdb command that does that but I can't
remember what.
Thanx,
Jason
--
Jason Bobier email@hidden
PGP Corporation
www.pgp.com
________________________________________________________________
This message could have been secured by PGP Universal. To secure
future messages from this sender, please click this link:
https://keys.prismatix.com/b/b.e?r=xcode-users%
40lists.apple.com&n=6uAtk9mV5ej9EgCQKEqRoQ==
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40prismatix.com
This email sent to email@hidden
________________________________________________________________
This message could have been secured by PGP Universal. To secure
future messages from this sender, please click this link:
https://keys.prismatix.com/b/b.e?r=xcode-users%
40lists.apple.com&n=6uAtk9mV5ej9EgCQKEqRoQ==
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40verizon.net
This email sent to email@hidden
________________________________________________________________
This message could have been secured by PGP Universal. To secure
future messages from this sender, please click this link:
https://keys.prismatix.com/b/b.e?r=xcode-users%
40lists.apple.com&n=RiY2a7BlpPT8dKEqnPdCpQ==
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com
This email sent to email@hidden
________________________________________________________________
This message could have been secured by PGP Universal. To secure
future messages from this sender, please click this link:
https://keys.prismatix.com/b/b.e?r=email@hidden&n=gFm%
2FPM67SxRZPwN2rd6Ltw==
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden