> 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?
Sorry, debugging stack corruption can be really hard, precisely because the
bug trashes the most helpful info... There's an Apple technote on debugging,
and one of the suggestions is look at registers to see if you recognize data
in them... First, can you reproduce the problem? If so, you can at least try
narrowing down the problem by methodically removing chunks of code to see
what code the problem follows. You can also try aggressively logging
information about the run, but adding the logging can shuffle things around
in memory and on the stack...
Of course, check (or remove) all fixed-size stack-allocated arrays, since a
bounds over/underrun is the quickest way to hose your stack...
--
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 722-0567 voice
_______________________________________________
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
This email sent to email@hidden
