Rubbish or nothing, it all sounds like a stack corruption to me.
Think carefully about memory accesses in the lead up to the crash
(what are the minimal bug reproduce conditions?). Also running on
intel may tell you more if do naughty memory things...
On 30/06/2006, at 9:20 AM, Peter CK wrote:
On 6/29/06, Rua Haszard Morris <email@hidden>
wrote:
Hmm, it sounds as though the app has corrupted the stack, we have had
this on occasion - the Xcode debugger (as you've seen with other
projects) does give you a call stack on crash, but if it crashes
after a mem corruption that has corrupted the stack, it'll give you a
corrupted stack (i.e. rubbish).
Yes, there is mention of a corrupt stack. I don't recall seeing any
rubbish. I think the call stack is just blank. Is there any way I
can debug this?
Thanks,
Peter
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/xcode-users/r.haszardmorris%
40adinstruments.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:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
