[EMAIL PROTECTED] wrote:
> I know that a core dump is a memory dump to the harddisk. How can I use this
> to ? How do I use the core file to determine where the bug is ?
gdb -c /path/to/core
Unless the executable (and possibly libraries) were compiled with
debug info (`gcc -g ...'), this is of limited use, although you can
still get a stack backtrace with gdb's `where' command (unless the
executable/libraries were compiled with -fomit-frame-pointer, in which
case the core file is virtually useless).
--
Glynn Clements <[EMAIL PROTECTED]>
