WEll that's during debugging. I'm trying to log it during a beta
tester run. I don't want it to crash, but just during some debugging
with these testers I want to see what methods call it when in relation
to other things happening. In our tests it should only happen in
specific situations,
On Apr 20, 2009, at 23:09 , Alex Kac wrote:
I am trying to log some specific error conditions in a fairly
dynamic environment (of course Obj-C's forté), and would like to log
some sort of backtrace of method calls that reached a specific method.
What is the best way to get that info? This
On Apr 21, 2009, at 11:27 AM, Alastair Houghton wrote:
On 21 Apr 2009, at 15:59, Michael Ash wrote:
On Tue, Apr 21, 2009 at 2:09 AM, Alex Kac wrote:
I am trying to log some specific error conditions in a fairly
dynamic
environment (of course Obj-C's forté), and would like to log some
sort
On 21 Apr 2009, at 15:59, Michael Ash wrote:
On Tue, Apr 21, 2009 at 2:09 AM, Alex Kac wrote:
I am trying to log some specific error conditions in a fairly dynamic
environment (of course Obj-C's forté), and would like to log some
sort of
backtrace of method calls that reached a specific met
On Tue, Apr 21, 2009 at 2:09 AM, Alex Kac wrote:
> I am trying to log some specific error conditions in a fairly dynamic
> environment (of course Obj-C's forté), and would like to log some sort of
> backtrace of method calls that reached a specific method.
>
> What is the best way to get that info
Hey,
The first thing that comes to mind is throwing an exception, catching
it, then accessing the NSException's -callStackReturnAddresses. From
there, you'll need to turn the addresses into symbol names. I googled
it a little bit and found these references:
http://developer.apple.com/documentatio
I am trying to log some specific error conditions in a fairly dynamic
environment (of course Obj-C's forté), and would like to log some sort
of backtrace of method calls that reached a specific method.
What is the best way to get that info? This is using Objective-C 2.0
on the iPhone.
Al