The simplest way is to just do abort(). 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.
David On 15 Jun 2012, at 11:36, Andreas Höschler wrote: > 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. > > Thanks a lot, > > Andreas > > > _______________________________________________ > Discuss-gnustep mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/discuss-gnustep -- Sent from my STANTEC-ZEBRA _______________________________________________ Discuss-gnustep mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnustep
