Crash dump

Is there any reference to learn on reading the crash dump report?
Especially the stack dump, the exception code.
Is there any way to trace back to the exact line of C code that causes the crash of Squeak VM?

2009/3/3 Ang Beepeng <[hidden email]>:
>
> Is there any reference to learn on reading the crash dump report?
> Especially the stack dump, the exception code.
> Is there any way to trace back to the exact line of C code that causes the
> crash of Squeak VM?

well, if you build VM with debug info, you could load it in gdb and
then go to the address of exception to see the code where it thrown.

> --
> View this message in context: http://www.nabble.com/Crash-dump-tp22314485p22314485.html
> Sent from the Squeak - Dev mailing list archive at Nabble.com.
>
>
>



--
Best regards,
Igor Stasenko AKA sig.

Igor Stasenko wrote

2009/3/3 Ang Beepeng <beepeng86@yahoo.com>:
>
> Is there any reference to learn on reading the crash dump report?
> Especially the stack dump, the exception code.
> Is there any way to trace back to the exact line of C code that causes the
> crash of Squeak VM?

well, if you build VM with debug info, you could load it in gdb and
then go to the address of exception to see the code where it thrown.

What do you mean by debug info specifically?  

Thank you so much.

Ang Beepeng

2009/3/3 Ang Beepeng <[hidden email]>:
mainly, a compiler directive -g
and remove "strip" command in makefile to keep symbol information in
executable file.
Then you can use gdb to look for a source code at concrete instruction address.

>
> Ang Beepeng
> --
> View this message in context: http://www.nabble.com/Crash-dump-tp22314485p22315601.html
> - Show quoted text -
> Sent from the Squeak - Dev mailing list archive at Nabble.com.
>
>
>



--
Best regards,
Igor Stasenko AKA sig.