Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Wrong stack when debugging CFM app under Rosetta

Durango wrote: 
On Mon, Aug 6, 2007 6:14 AM, Stephen Chu <email@hidden> wrote:

Or in the crash report. We ran into some Intel-only crashes with our PPC CFM app. The Stack trace in the reports are just numbers. We can't even find out what the app is doing at the time of crash.

All of those I ran into were caused by uninitialized variables.

What the bug is really isn't the point. The point is to have a meaningful stack trace for us to work with.

BTW. The crashes we ran into have nothing to do with uninitialized variables. One is a missing font from the system (God/Allah/Buddha knows why the user deleted it and why it even matters) while the other a mysterious AppleEvent issue involving AFP mounts that we never actually understood or fixed, only to awkwardly work around.

In either case, a meaningful crash log would have saved us weeks of time trying to pin point the location within our code with thousands of printf/CFShow calls.

--
Stephen Chu <mailto:email@hidden>
Rampage Systems, Inc. <http://www.rampageinc.com/>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden

This email sent to email@hidden
References: 
 >Re: Wrong stack when debugging CFM app under Rosetta (From: "Jan Barnholt" <email@hidden>)
 >Re: Wrong stack when debugging CFM app under Rosetta (From: Stephen Chu <email@hidden>)
 >Re: Wrong stack when debugging CFM app under Rosetta (From: Durango <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.