Re: prevent gdb stepping into dyld_stub_XXX on step over?
Re: prevent gdb stepping into dyld_stub_XXX on step over?
- Subject: Re: prevent gdb stepping into dyld_stub_XXX on step over?
- From: Dave Camp <email@hidden>
- Date: Tue, 5 Feb 2008 16:13:57 -0800
On Feb 5, 2008, at 3:46 PM, Jim Correia wrote:
On Jan 21, 2008, at 4:44 PM, Jim Correia wrote:
I have a project that I was previously building with Xcode 2.4 on
10.4.x.
I'm now building the project with Xcode 3 on 10.5.1.
When I "Step Over" in the debugger, I often end up in "runtime"
code I don't care about. Examples of this are dynamic casts and
ending up in dyld_stub_XXX (dyld_stub_GetWindowBounds is a concrete
example.) This did not happen with Xcode 2.4 (And I don't see it
when building sample projects with Xcode 3.0)
How can I prevent this?
I'm still experiencing this problem. I've compared my debug settings
to those in the sample project and don't see anything obvious
differences. I have experimented with changing the debug level,
dwarf vs. stabs, inlining levels, and still consistently see the
problem when using the Xcode source level debugger.
Interestingly enough, if I step over the same code using gdb from a
terminal session, I do not see the problem.
Has anyone run into this, and come up with a solution?
I had this problem once and I think turning off Load Symbols Lazily in
the Xcode Debugger prefs fixed it, but I'm not 100% on that...
Dave
_______________________________________________
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