Re: Shark logs provided by users
Re: Shark logs provided by users
- Subject: Re: Shark logs provided by users
- From: Nathan Slingerland <email@hidden>
- Date: Mon, 28 Nov 2005 10:02:53 -0800
The ability to symbolicate Shark session files is something we're
working on for an upcoming release.
Sorry that this capability isn't yet available.
--
Nathan Slingerland
Architecture and Performance Group
Apple Computer, Inc.
On Nov 28, 2005, at 9:58 AM, Nathan Herring wrote:
On 11/28/05 9:32:53 AM, "Marshall Clow" <email@hidden> wrote:
Have you guys looked at macprang? <http://macprang.sourceforge.net/>
Erm, so what is this then?
An open-source, BSD-licensed Python program that can apply a
CodeWarrior CFM link map to a Mac OS X crash log.
Why would I want that?
Typically because you've configured the release build of your
CodeWarrior Carbon CFM app to omit traceback tables, for space and/or
privacy reasons, and therefore can't readily interpret crash logs
from your release builds, because they show backtraces as pure hex
addresses. This program can decode the hex addresses into function
names and offsets, just like your debug build.
Thanks for the pointer, but again, we can work with crash logs fine
already,
with our own scripts. However, we would like to apply the same
logic to
.mshark session files, preferrably through direct manipulation of
an .mshark
file or by creation of static (I hope) auxilliary files (like
Shark's patch
files).
Any tips on _that_?
Or am I missing something wrt macprang?
-nh
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com
This email sent to email@hidden
_______________________________________________
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