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 HPUX
vpardump
vpardump(1M)vpardump(1M)NAME
vpardump - manage monitor dump files
SYNOPSIS
[vparmon[dumpfile]]
DESCRIPTION
The command is used to create (on PA-RISC systems only) and analyze a virtual partition monitor dump file. vparmon is the image of the
virtual partition monitor and dumpfile is the crash dump file corresponding to that image. is normally run from the rc script to analyze a
crash dump during HP-UX boot. If no options are specified, checks if the dumpfile has been cleared. If not, it analyzes dumpfile and
prints information about the crash to standard out. Then marks the dumpfile as clear. If dumpfile is not specified, the string is
appended to vparmon as in If vparmon is not specified, it defaults to
The dumpfile must exist prior to a vpar monitor crash. On PA-RISC systems, the and options create the dumpfile on PA-RISC. If is used, a
dumpfile is created that is large enough to contain the monitor image. If additional structures are required, such as I/O Page Directo-
ries, the option is used to reserve space for a full monitor crash dump. On Itanium(R)-based systems, the monitor dumpfile is created in
the EFI partition of the monitor's boot disk as needed. It is not necessary to pre-allocate a dump file in A monitor dump typically
requires less than 75 megabytes of free space in the EFI partition. In order to ensure that a complete crash dump can be saved, this much
free space must be maintained in the EFI partition.
Options
recognizes the following command-line options:
Analyze the
dumpfile. This option can be used to force an analysis even if dumpfile has been cleared.
Mark dumpfile as clear. No analysis is performed.
Analyze
dumpfile even if the versions do not match.
Initialize
dumpfile for a full dump. Supported only on PA-RISC systems.
Initialize
dumpfile for a normal dump. Supported only on PA-RISC systems.
Do not analyze the
dumpfile.
Enable verbose output.
The and options are allowed on Itanium-based systems for compatibility. No action is taken for the and options.
Operands
recognizes the following command-line operands:
vparmon The name of the image of the virtual partition monitor. If vparmon is not specified, it defaults to
dumpfile The name of the crash dump file corresponding to the image of the virtual partion monitor. If dumpfile is not specified,
the string is appended to vparmon as in
Security Restrictions
This command is restricted to processes owned by superuser or with the privilege. See privileges(5) for more information about privileged
access on systems that support fine-grained privileges.
RETURN VALUE
returns the following values:
Analyzed
dumpfile successfully.
Created a new
dumpfile.
A dumpfile does not exist.
The dumpfile is cleared, no action taken.
Error attempting to create a
dumpfile.
Error analyzing the
dumpfile.
Command syntax error.
EXAMPLES
Analyze the default dumpfile and create it if it does not exist:
Suppress the analysis of the default dumpfile, and reserve space for a full dump:
AUTHOR
was developed by the Hewlett-Packard Company.
SEE ALSO vparextract(1M), privileges(5).
vpardump(1M)