Re: Debugger at odds with reality?
Re: Debugger at odds with reality?
- Subject: Re: Debugger at odds with reality?
- From: Keary Suska <email@hidden>
- Date: Sat, 26 Apr 2008 08:31:55 -0600
- Thread-topic: Debugger at odds with reality?
on 4/26/08 7:20 AM, email@hidden purportedly said:
> I have a funny problem which is proving difficult to fix.
>
> I have a framework which I've written, and an app which I've written
> that uses it. I can debug to my heart's content in both - make a
> change in the framework, the change is reflected in the app, all is
> well.
>
> Now I'm trying to help someone out who is also writing an app against
> my framework, and things there are totally weird. I've set up the app
> project identically to my own app (AFAICS) but there are two debugging
> problems which I don't get in my own app. The first is that
> breakpoints in the framework don't cause a break. The second much
> worse problem is that the layout of objects is wrong - it's as if the
> debugger is using some (much) older version of the framework classes
> for its symbol definitions, so when the code tries to set an ivar say,
> some other part of the object gets updated in the debugger. From what
> I can tell the code is right, as things are actually working, but the
> debugger has an out of date view of the code.
>
> Where does the debugger grab its "picture" of the linked framework from?
The first thing I would try is deselecting "lazy symbol loading" under Xcode
preferences (debugging).
HTH,
Keary Suska
Esoteritech, Inc.
"Demystifying technology for your home or business"
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden