core dump reading

[Inesa Clinko]

Good Morning!

Please help me to "read" core-dump file in order to find out the problem. I know that I could use "adb", but how? My system is PA-RISK 11.11.
Core dump is:"/root/core" from 15/10/2006.

[Jaime Bolanos Rojas.]

Inesa,

You might want to try with:

strings core | grep -i fatal

Regards,

Jaime.

[Peter Nikitka]

Hi,

to identify the program that created the core file, run the command
file /path/to/core

If the program name is one of your self developped ones, load program and core in the debugger.

mfG Peter

[rariasn · Accepted solution]

Hi Inesa,

Sampel "gdb"

# file /oracle/oraclesid/scripts/core

ELF-64 core file - PA-RISC 2.0 from 'sqlplus' - received SIGQUIT

# gdb /opt/oracle92/bin/sqlplus /home/oracle/oraclesid/scripts/core

...
(gdb) bt

#0 0xc0000000002fc3ec in adjtime+0x44 () from /usr/lib/pa20_64/libc.2
#1 0xc000000000307124 in wait3+0x94 () from /usr/lib/pa20_64/libc.2
Error accessing memory address 0x0: Invalid argument.

(gdb) quit

rgs

[Senthil Prabu.S_1]

Hi,
GDB is a useful tool for debugging core files generated by processes.

To find out more information regarding GDB visit;
http://www.gnu.org/software/gdb/documentation/

Running GDB

[a]. Determine the location of GDB, whereis gdb
[b]. Execute gdb from the directory returned by the whereis command. Note the arguments to gdb are
Process
Core file location
[c]. Example, to analysis the core file core.225 located in the /home/mcadmin/CORE-FILES/applications directory which was generated by the mobi process run gdb as follows

gdb /apps/picasso/bin/mobi /home/mcadmin/CORE-FILES/applications/core.225

[a]. To gather backtrace useful to analysis the problem type bt
[b]. Save this backtrace to a file
[c]. To quit gdb, type quit