Re: Shark logs provided by users
Re: Shark logs provided by users
- Subject: Re: Shark logs provided by users
- From: Marshall Clow <email@hidden>
- Date: Mon, 28 Nov 2005 09:32:53 -0800
At 9:30 AM -0800 11/28/05, Nathan Herring wrote:
We indeed do something similar, though not with atos, for CrashReporter
logs. However, for CFM libraries and for bundles, i.e., 99% of the code in
Office 2004, you still need to know where it was loaded, and it is not
obvious exactly where that would be stored in an .mshark file. We could
probably do some per-library guessing, but would rather take a deterministic
approach.
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.
--
-- Marshall
Marshall Clow Idio Software <mailto:email@hidden>
It is by caffeine alone I set my mind in motion.
It is by the beans of Java that thoughts acquire speed,
the hands acquire shaking, the shaking becomes a warning.
It is by caffeine alone I set my mind in motion.
_______________________________________________
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