Uh, 'file core' is a bit faster:
[wegster@voyager wegster]$ ls core
core
[wegster@voyager wegster]$ file core
core: ELF 32-bit LSB core file of 'gnome-help-brow' (signal 6), Intel
80386, version 1
Also, 'strings core | head' can be useful on systems that 'file' doesn't
work on(think HP/UX and a few others dont work 'right' like this..)
[wegster@voyager wegster]$ strings core | head
CORE
CORE
gnome-help-brow
gnome-help-browser
CORE
gnome-help-brow
#9B573B
c #995437
c #975235
c #945034
Broken pipe
[
Hope that makes life a bit easier..
david wrote:
>
> Marin D wrote:
>
> > Hi,
> >
> > How could I know which executable has dumped a core by simply looking at
> > the dumped core file? Is the name quoted in the very beginning of the core
> > as I think?
>
> I use a little trick :
>
> $ gdb ls core
> GDB is free software and you are welcome to distribute copies of it
> under certain conditions; type "show copying" to see the conditions.
> There is absolutely no warranty for GDB; type "show warranty" for details.
> GDB 4.16 (i586-debian-linux), Copyright 1996 Free Software Foundation, Inc...
>
> (no debugging symbols found)...
>
> warning: core file may not match specified executable file.
> Core was generated by `cdrecord -v speed=4 fs=8 dev=s -isosize
> /dev/hdd'.
> Program terminated with signal 11, Segmentation fault.
> ...
>
> As you see when you give a program that don't match the core file , gdb
> will tell you what command has generated the core.
>
> david
--
===========================================================================
= Scott Wegener | Email: [EMAIL PROTECTED]
= Software Engineer | [EMAIL PROTECTED]
= Alphatronix | Web: http://www.alphatronix.com
= Raleigh, NC | Personal: http://members.tripod.com/~wegster
===========================================================================
= There can be no greater Hell known to man than that of those who
= have been forced to program in COBOL.
===========================================================================
