You have a stack trace. Unfortunately I'm in front of a PC right now, but
the path is something like:
/System/Logs/CrashReporter/YourAppName.log
Or something like that. Agreed it would be nice if XCode would bring up your
stack trace when your app core dumps.
Tim
-----Original Message-----
From: xcode-users-bounces+tjhart=email@hidden
[mailto:xcode-users-bounces+tjhart=email@hidden] On Behalf Of
Peter CK
Sent: Thursday, June 29, 2006 8:55 AM
To: XCode Users List
Subject: Re: Re: can I catch an EXC_BAD_ACCESS?
> I think the problem is that this list has recently seen a pretty
disturbing
> number of requests from programmers who have memory bugs and actually are
> looking for a way to ignore them. The precedent has been set, if you don't
> explicitly state the above, then we're likely to assume you're another
> clueless twerp looking for an easy way to avoid debugging his code ;-)
In my case, there very well could be memory bugs that I could fix.
Hmmm.... if only xcode would be so kind to provide me with a call
stack. Is it honestly just me, or does this software feal like it's an
alpha release.
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/email@hidden
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
This email sent to email@hidden
