Basically, you use a debugger. Since you did not specify an OS I'll assume you have
gdb. You must have compiled the file
in order for symbols to be available. If you are analyzing a core dump of somebody else's code you are in trouble.
The core dump file is called core
This will show you a backtrace (stack dump) of the call tree that lead to the crash.
You will have to find using the stack dump where in the code (not in a C library) the crash occurred. In other words the last line of the program's code that actually led to the crash.
Hi folks,
I'm hoping someone would be charitable enough to give me a quick explanation of adb usage for analyzing core files...or point me in the right direction. A search here revealed scant results and web searches are providing me with ambiguous information.
Running Solaris.
Thanks,... (1 Reply)
Hi,
I just wanted to know is there any tool avaliable for core analysis on hp-ux. I have heard about q4 utility. But I think it is used for analysis of system crash dump and not for core dump produced by a user process.
gdb doesn't give much information unless the binary is debug-build.
... (0 Replies)
Hello,
I'm new to the group and this is my first post. I'm hoping someone can help me out. I have a core dump that I need to analyze from a Unix box and I've never done this sort of thing before. I was told to run a pmap and pstack on the core file which provided two different output files. ... (3 Replies)
How can we analyze a core file and determine why it was generated on a solaris system?
I know file core filename will tell us what program generated the file. But, what to do next to get more details?
Thanks, (5 Replies)
We have just enabled core dump on our RHEL5.7 OS. the java process is terminating very often so we enable core dump to analysis the issue and find below in core dump file.
Core was generated by `/usr/java/jdk1.6.0_06//bin/java -server -Xms1536m -Xmx1536m -Xmn576m -XX:+Aggre'.
Program... (0 Replies)
dear all,
i have p770 aix6.1
last week, the host reboot suddenly with dump. but i don't know how to analyze the dump.
I posted kdb details in the attachment.
please anybody help me.
#>kdb vmcore.0 /unix
vmcore.0 mapped from @ 700000000000000 to @ 7000001c72c0908
START ... (13 Replies)
Discussion started by: tomato00
13 Replies
LEARN ABOUT CENTOS
systemd-coredumpctl
SYSTEMD-COREDUMPCTL(1) systemd-coredumpctl SYSTEMD-COREDUMPCTL(1)NAME
systemd-coredumpctl - Retrieve coredumps from the journal
SYNOPSIS
systemd-coredumpctl [OPTIONS...] {COMMAND} [PID|COMM|EXE|MATCH...]
DESCRIPTION
systemd-coredumpctl may be used to retrieve coredumps from systemd-journald(8).
OPTIONS
The following options are understood:
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
-F, --field=
Print all possible data values the specified field takes in matching coredump entries of the journal.
-o, --output=FILE
Write the core to FILE.
--no-pager
Do not pipe output of list into a pager.
--no-legend
Do not print the column headers.
The following commands are understood:
list
List coredumps captured in the journal matching specified characteristics.
dump
Extract the last coredump matching specified characteristics. Coredump will be written on stdout, unless an output file is specified
with -o/--output.
gdb
Invoke the GNU debugger on the last coredump matching specified characteristics.
MATCHING
Match can be:
PID
Process ID of the process that dumped core. An integer.
COMM
Name of the executable (matches COREDUMP_COMM=). Must not contain slashes.
EXE
Path to the executable (matches COREDUMP_EXE=). Must contain at least one slash.
MATCH
General journalctl predicates (see journalctl(1)). Must contain an equals sign.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise. Not finding any matching coredumps is treated as failure.
SEE ALSO systemd-journald.service(8), gdb(1)systemd 208SYSTEMD-COREDUMPCTL(1)