Re: Shark is losing source code
Re: Shark is losing source code
- Subject: Re: Shark is losing source code
- From: Rick Altherr <email@hidden>
- Date: Fri, 6 Jun 2008 12:17:03 -0700
On Jun 6, 2008, at 12:06 PM, kwiley wrote:
Okay, so I tried this both on a file/function that Shark does find
and show source for and on one that Shark fails to find source for.
In both cases it worked. It said it found it. So dwarfdump can
follow the .dSYM to the source, but Shark fails to do so.
How do I know for certain that Shark is using the .dSYM at all?
Generally, Shark works more or less without a .dSYM. It was
suggested that I manually make the .dSYM and put it next to the
executable, but since Shark's behavior is absolutely identical, it
looks from my point of view like nothing has changed, as if it isn't
using the .dSYM...all of this still raises the question of why
manually making a .dSYM would be necessary any way, since I don't
believe the .o or .a files have been mangled after compilation, but
that's a side issue I suppose.
Thanks again.
________________________________________________________________________
Keith Wiley email@hidden http://www.cs.unm.edu/~kwiley
"The easy confidence with which I know another man's religion is folly
teaches me to suspect that my own is also."
-- Mark Twain
________________________________________________________________________
The reason that making a .dSYM is necessary in this case is due to a
bug in Shark's handling of .a's when dealing with DWARF. Our next
release resolves that bug. In the meantime, making a .dSYM is a
workaround. The .dSYM should be placed in the same directory as the
main executable. Note that if this is a bundle
(.bundle, .app, .framework, etc), the .dSYM should be next to the
bundle, not the binary within the bundle. If you you are simply
building a command-line tool, just place the .dSYM in the same
directory.
Shark will use the .dSYM if it fails to find debug information from
the main executable. So, now that you have generated the dSYM, run
strip -S on the executable. Finally, just to be safe, restart Shark.
That will clear any internal caches of debug information for the binary.
--
Rick Altherr
Architecture and Performance Group
email@hidden
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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