Re: how to find a segfault?
Re: how to find a segfault?
- Subject: Re: how to find a segfault?
- From: Brent Gulanowski <email@hidden>
- Date: Fri, 9 Jul 2004 17:14:52 -0400
On Jul 9, 2004, at 4:50 PM, Markian Hlynka wrote:
> Ok, my program has a seg fault:
>
>> myMona has exited due to signal 11 (SIGSEGV).
>
> if I was using gdb/gcc on the CLI, I'd run it through GDB and type
> "where".
>
> I did this on the console drawer in xcode's debugger, and I get a note:
>
>> GDB: Loading 104819 stack frames... (9%)
>
> now, it's going up VERY slowly. too slowly to be useful.
>
> Am I doing something wrong? suggestions?
You are caught in a recursive loop. In AppKit this tends to result from
overriding a method and calling some other method that calls (or sets a
flag that results in a successive call to) the overridden method. I
usually just put a break point in a few likely places and see which one
reveals the recursion in the stack.
--
Brent Gulanowski email@hidden
[demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.