Core Dump
Any error that cannot be trapped by an application program (assuming the
error is such that the OS is still in control) should result in "core dump".
Typical causes: Invalid OP Code, Invalid or out range memory addresses etc.
Majority of the cases this happens because of Invalid Pointers to Objects
like Buffers, Code location etc.
Unless you are an expert at identifying the Current Instruction Pointer,
Status Register contents, General Register contents, and your code and data,
there is no point in staring at a Core Dump.
Yes you must be an expert at Assembly Language, with a flair for realigning
with addresses on Little-endian format (for Intel core dumps).
JPM
>I am not sure exaclty how the core dump is produced, but basicaly on most
>fatal fualts,the process is killed and 'core dumped' i.e the image of the
>process in memory is dumped(i think).To debug this run it in gdb, i.e "gdb
>a.out core".Also it is a good idea to complie the proggy with -g flag
>(debugging symbols not stripped).
>Hope its of some help.
>
>sapsi
>[EMAIL PROTECTED]
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
--
To unsubscribe, send mail to [EMAIL PROTECTED] with the body
"unsubscribe ilug-cal" and an empty subject line.
FAQ: http://www.ilug-cal.org/faq/listfaq.html
