Re: Debugging a process that received Signal
Re: Debugging a process that received Signal
- Subject: Re: Debugging a process that received Signal
- From: Joel Reymont <email@hidden>
- Date: Sat, 31 Jan 2009 12:49:18 +0000
On Jan 31, 2009, at 12:40 PM, Arnab Ganguly wrote:
I want to compare the stack trace generated by program matches with
the
Crashreporter.app or not.
Does crash reporter tell you the function where the crash happens or
just give you hex addresses?
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.
So you figured from crash reporter where to force your segmentation
violation, right?
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?
When you run this program in gdb, does it drop into the debugger
prompt once the violation happens? You can also attach to the program
with gdb once it's running.
Just type "where" at the gdb prompt after the violation to get your
stack trace.
---
http://tinyco.de
--- Mac & iPhone
_______________________________________________
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