Re: how to find a segfault?
Re: how to find a segfault?
- Subject: Re: how to find a segfault?
- From: Jim Ingham <email@hidden>
- Date: Fri, 9 Jul 2004 14:23:36 -0700
Sounds like you have an infinite recursion that has eventually blown
off the top of the stack. Xcode is busy fetching ALL those stack
frames from gdb, which could take a while... I don't think there is a
way to tell Xcode not to load all the frames in a backtrace. In
command-line gdb you can use the "backtrace 10" command to just see the
last 10 entries on the stack. Also, if you just run the app normally,
when it crashes you should be able to look at the crashreporter log,
and that will tell you where the crash was.
You can
Jim
On Jul 9, 2004, at 1: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?
_______________________________________________
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.
_______________________________________________
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.