Re: Triggering core dump creation

[Andreas Höschler]

Hey David,

> The simplest way is to just do abort().

Thanks a lot!! I will do that!

> If you just want a stack trace, you can create an NSException and then read 
> the stack trace from it and print it before (or instead of) throwing.  

The problem ist i can't reproduce the problem at will so running the app in gdb 
is no option. I have to wait until it occurs again in the production system.
> 
>> Hi all,
>> 
>> I am trying to track down a problem that occurs only every 6 weeks or so 
>> (impossible to reproduce at will). I am raising an exception 
>> 
>>        [NSException raise:NSInternalInconsistencyException format:@"%@", 
>> message];
>> 
>> when the problem occurs. This exception is catched and the message presented 
>> in a panel. 
>> 
>> Is there any way to programmatically cause a core dump instead of raising 
>> the exception? I need a back trace to find the cause of the problem.
>> 
> 


Best wishes,

 Andreas