On Mon, Aug 6, 2007 11:27 AM, Stephen Chu <email@hidden> wrote:
>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.
Shrug.
Just trying to save you the time spent complaining about the lack of a
stack trace. One doesn't always get what one wants, but the bugs have to
be eliminated anyway.
Sorry if I missed that all you were looking for was sympathy.
_______________________________________________
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
