Re: Error fixing... Object '(null)' not found.
Re: Error fixing... Object '(null)' not found.
- Subject: Re: Error fixing... Object '(null)' not found.
- From: Jason Molenda <email@hidden>
- Date: Wed, 11 Aug 2004 15:25:51 -0700
Hi Fritz,
On Aug 11, 2004, at 12:32 PM, Fritz Anderson wrote:
In Xcode 1.5, whenever I attempt a fix-and-continue, the debugger
displays an alert
Fix and Continue
Error fixing SourceFile.m. Object '(null)' not found.
There's a bug we're pursuing where the build system seems to build
fix-and-continue bundles with the deployment build style instead of the
development build style. The resulting optimized file is not legal for
fix and continue and gdb throws up this (less than helpful) error while
trying to fix it in.
We have a bug report tracking this issue; if you can give me some idea
of your steps leading up to this I'll add the information to the
report. I've personally seen this when I open a project from scratch
that has been built already, start debugging it ("Debug", not "Build &
Debug") and do the Fix. I've heard of other people hitting the same
problem but possibly with different start-up scenarios.
You can confirm that this is the problem by opening the Detailed Build
Results (shift cmd B) and splitting the window into three parts -- the
middle part (not visible when you first open the window) has the
command lines passed to the compiler. When you see a "-Os" type
optimization flag in a fix-and-continue build, that's a clear sign that
something is not right.
Jason
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.