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 DEBIAN
rivet
RIVET(1) User Commands RIVET(1)NAME
rivet - Robust Independent Validation of Experiment and Theory
SYNOPSIS
rivet [options] myfifo
OPTIONS --version
show program's version number and exit.
-h, --help
show this help message and exit.
-l NATIVE_LOG_STRS
set a log level in the Rivet library.
-a ANA, --analysis=ANA
add an analysis to the processing list.
--list-analyses
show the list of available analyses' names. With -v, it shows the descriptions, too.
--list-used-analyses
list the analyses used by this command (after subtraction of inappropriate ones).
--show-analysis=SHOW_ANALYSES, --show-analyses=SHOW_ANALYSES
show the details of an analysis.
--analysis-path=PATH
specify the analysis search path (cf. $RIVET_ANALYSIS_PATH).
--analysis-path-append=PATH
append to the analysis search path (cf. $RIVET_ANALYSIS_PATH).
--pwd append the current directory (pwd) to the analysis search path (cf. $RIVET_ANALYSIS_PATH).
-H HISTOFILE, --histo-file=HISTOFILE
specify the output histo file path (default = Rivet.aida).
-x XS, --cross-section=XS
specify the signal process cross-section in pb.
-n NUM, --nevts=NUM
restrict the max number of events to read.
--runname=NAME
give an optional run name, to be prepended as a 'top level directory' in histo paths.
--ignore-beams
Ignore input event beams when checking analysis compatibility.
--event-timeout=NSECS
max time in whole seconds to wait for an event to be generated from the specified source (default = 21600)
--run-timeout=NSECS
max time in whole seconds to wait for the run to finish. This can be useful on batch systems such as the LCG Grid where tokens
expire on a fixed wall-clock and can render long Rivet runs unable to write out the final histogram file (default = unlimited).
--histo-interval=HISTO_WRITE_INTERVAL
[experimental!] specify the number of events between histogram file updates. Default is to only write out at the end of the run.
Note that intermediate histograms will be those from the analyze step only: analysis finalizing is currently not executed until the
end of the run.
-v, --verbose
print debug (very verbose) messages.
-q, --quiet
be very quiet.
EXAMPLES
mkfifo hepmc.fifo
my-generator -o myfifo &
rivet --analysis=ANALYSIS_NAME hepmc.fifo
ENVIRONMENT :
RIVET_ANALYSIS_PATH
list of paths to be searched for plugin analysis libraries at runtime.
RIVET_REF_PATH
list of paths to be searched for reference data files.
RIVET_INFO_PATH
list of paths to be searched for analysis metadata files.
AUTHOR
This manual page was written by Lifeng Sun <lifongsun@gmail.com> for the Debian system (but may be used by others).
Rivet June 2012 RIVET(1)