Re: Debugging a process that received Signal
Re: Debugging a process that received Signal
- Subject: Re: Debugging a process that received Signal
- From: Arnab Ganguly <email@hidden>
- Date: Sat, 31 Jan 2009 18:10:38 +0530
I want to compare the stack trace generated by program matches with the Crashreporter.app or not.Now in successful case there is no crash log generated for the app so I am trying forcibly the segmentation fault just to compare the stack traces generated by my app and with the Crashreporter. But when the segmentation fault happens, as you said earlier I am not able to proceed with my code to see how the trace comes up in my app.Is there any workaround for this?
Thanks in advance
Arnab
On Sat, Jan 31, 2009 at 2:12 PM, Joel Reymont
<email@hidden> wrote:
On Jan 31, 2009, at 7:33 AM, Arnab Ganguly wrote:
Initially from gdb it is being debugged.Once the SIGNAL like SEGMENTATION
FAULT is received the gdb gets halted.Even going for "continue" I am not
able to proceed.
More likely than not, you have a null pointer reference or some such. Take a look at your code and set a breakpoint about the line number in the gdb stack trace. Run your program again.
Once you get to the breakpoint, proceed carefully, step line by line and inspect your variables until you figure out what is wrong. Fix, recompile and re-run.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden