[Wylug-help] Help with Linux core file.
Thomas, Nicholas
nick.thomas at eldon.co.uk
Mon Mar 22 10:16:10 GMT 2004
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Hi,
My user space app has produced a core file. I usually run:
gdb -c core.xxx
To make sure that the core file was generated by my suspect app.
Then I run:
gdb appname core.xxx
To attempt to debug it.
Normally gdb will first load all of the shared libraries and then it will
try to show me where the crash happened.
However, this time I have a 270MB core file !!! And when I run "gdb appname
core.xxx" All I get is:
---------------------------------------
GNU gdb 5.0
Copyright 2000 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or 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.
This GDB was configured as "i686-pc-linux-gnu"...
Core was generated by `appname >>/tmp/SatExec.log'.
Program terminated with signal 11, Segmentation fault.
#0 0x4010738e in ?? ()
(gdb)
------------------------------------------
I can't believe that a 270MB core file only show me this info!!!
Anybody got any ideas?
I compiled the apps and libs with the -g option, and the output of gdb
usually does show me where in the source code the problem(s) are.
One thing, when this app crashed it also crashed the X server, and the
system automatically shutdown and rebooted. Could this have any significant
issue relating to my core file?
I am running a system based on RedHat 6.2 with kernel 2.4.17.
Any help appreciated.
Regards
Nick
_________________________
Nick Thomas
Leading Software Engineer
Eldon Technology Limited
Park House
College Road
Bingley
West Yorkshire, UK
BD16 4UD
Tel: +44 1274 568432
Fax: +44 1274 551561
Email: nick.thomas at eldon.co.uk
--
More information about the Wylug-help
mailing list