The newest version of the 'file' command will tell you what program it is that crashed and burned. You probably want to look into a program called 'gdb', or Gnu DeBugger. This following info from an rpm archive can explain it alot better then I ever could, so here it is: [phobet@Molly phobet]$ rpm -qif `which gdb` Name : gdb Relocations: (not relocateable) Version : 4.18 Vendor: MandrakeSoft Release : 10mdk Build Date: Tue 21 Dec 1999 06:58:35 PM EST Install date: Thu 20 Jan 2000 08:47:45 PM EST Build Host: jedi.mandrakesoft .com Group : Development/Debuggers Source RPM: gdb-4.18-10mdk.src.rpm Size : 1685972 License: GPL Packager : Chmouel Boudjnah <chmouel@mandrakesoft.com> Summary : A GNU source-level debugger for C, C++ and Fortran. Description : Gdb is a full featured, command driven debugger. Gdb allows you to trace the execution of programs and examine their internal state at any time. Gdb works for C and C++ compiled with the GNU C compiler gcc. If you are going to develop C and/or C++ programs and use the GNU gcc compiler, you may want to install gdb to help you debug your programs. "Sreenivas" <seenu@seeyes.co.in> wrote: > Hi, > How can analyze core files. ____________________________________________________________________ Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com. - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.rutgers.edu
