2/26    I assume GDB will allow me to do a trace on any core dump. correct?
        Is there a better way? (pedants:  if so what?)
        \_ I use gdb all the time to analyze core dumps. The problem is
           that gdb gives this facad of a horribly complicated debugger
           which scares people away.  You just need to start off with
           the basics. Compile and link everything with the -g option.
           That's all you need. you can invoke gdb from the shell or emacs
           by calling gdb a.out core (substitute a.out with your program).
           bt is you best friend for finding where a program crashes.
           You're on your own from there. It's sad, I'm not even a
           software engineer and I use debuggers more often than most of
           them do.
                \_ I use Java.  I don't need to debug.  My programs are
                   guaranteed bug-free by Sun.
        \_ i can't think of anything better than what gdb+emacs does.
           what feature do you need? -ali