Re: Crash Report
Re: Crash Report
- Subject: Re: Crash Report
- From: David A Rowland <email@hidden>
- Date: Thu, 1 Jun 2006 11:48:15 -0700
At 4:39 PM +0100 6/1/06, Quinn wrote:
At 16:10 +0200 2/6/06, Dalton Hamilton wrote:
Does the below snippet of the Crash Report mean that the app
crashed on line 1586 of the method [MyAppIVC
mountIndex:DisplayMessages:] ??
No, it means that you crashed at offset 1586 into that routine.
Please pardon me if the following comments are too elementary.
Crashing is almost always the result of dereferencing (reading or
writing through) an invalid pointer.The possiblities are:
pointer is 0 (legitimate at the end of a list but fatal to dereference)
pointer is uninitialized and thus random (a good candidate for
intermittent failures)
pointer has been stepped on by a bad write through another pointer
(also can be intermittent)
an array bound has been exceeded (data is damaged, and if the data is
a pointer then there may be a failure down the line. Or the reference
is far enough from the array as to be beyond legal memory.)
A million other things could be wrong, but on modern hardsware there
isn't much else that will produce a crash.
David
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden