From: John Stiles <email@hidden>
Date: October 14, 2004 8:36:53 PM EDT
To: "Gohara, David " <email@hidden>
Cc: Performance optimization list
<email@hidden>
Subject: Re: Shark is the BOMB!
Once Shark opens an executable to read its symbols etc, it leaves it
open. Other processes can't write to it. This leads to fun situations,
i.e. imagine this scenario:
(a) Build and launch your app via Xcode
(b) Shark it, and don't quit Shark when you're done
(c) Quit your app, change some stuff and rebuild it
At this point, even if you've rebuilt, the old code is still on the
hard drive because Shark still has it open.
Once you quit Shark you will be able to write to the app again.
CodeWarrior puts up a handy error message in this case but it sounds
like Xcode might just continue on, re-launching the old bits on the
hard disk.
On Oct 14, 2004, at 5:34 PM, Gohara, David wrote:
Hi All,
Regarding Shark, which I agree is great. I just installed the new
CHUD package (I previously had 4.0.0b11 installed). If I compile an
app with debug symbols on and profile the program Shark works fine.
But if I go and change the code, recompile (with Shark still open)
and reprofile the code in Shark doesn't update. I tried rebooting
the system just to be sure there weren't any old electrons floating
around etc... It seems to get Shark to update to the new code, I
have to shut it down and restart before each profiling session.
I uninstalled CHUD 4.0.0 final and reinstalled the beta and
everything worked fine again.
Has anyone else noticed this, or is there a caching feature that
is new that I missed in preferences? I'm using 10.3.5 and Xcode 1.5,
if that helps any.
Thanks in advance,
Dave
David W. Gohara, Ph.D.
Harvard Medical School
http://www.scianafilms.com
617-432-1216 (p)
617-432-4360 (f)
