06-20-2005
Thanks for yor reply.
Yes, that started the program. This is my testing program, but if I have a real program, I cannot reproduce the problem easily by simply re-run it because there could be thousands of inputs and I don't know where and how it can crash. The purpose of running gdb is to find the problem (postmortem analyze).
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
2. UNIX for Dummies Questions & Answers
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)
Discussion started by: kristy
1 Replies
3. UNIX for Advanced & Expert Users
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)
Discussion started by: shriashishpatil
0 Replies
4. UNIX for Advanced & Expert Users
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)
Discussion started by: kimblebee
3 Replies
5. AIX
Please tell me some methods to analyse core dump in AIX.:) (2 Replies)
Discussion started by: Mythili
2 Replies
6. Solaris
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)
Discussion started by: Pouchie1
5 Replies
7. Red Hat
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)
Discussion started by: pawankkamboj
0 Replies
8. UNIX for Dummies Questions & Answers
Can any body provide me some good link to learn to create and analyze linux user mode application / kernel module core dumps? (1 Reply)
Discussion started by: rupeshkp728
1 Replies
9. AIX
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
abrt-action-generate-core-backtrace
ABRT-ACTION-GENERA(1) ABRT Manual ABRT-ACTION-GENERA(1)
NAME
abrt-action-generate-core-backtrace - Generates coredump-level backtrace
SYNOPSIS
abrt-action-generate-core-backtrace [-v] [-r] [-d DIR]
DESCRIPTION
This tool uses coredump from the file coredump and binary at the path stored in file executable in the problem directory to generate
coredump-level backtrace.
Coredump-level backtrace resembles ordinary backtrace in that it contains information about call frames present on the stack at the time of
the crash. However, it only contains information that can be obtained from the coredump without debugging symbols available - mainly
relative addresses of the stored instruction pointers. Such backtrace can still be useful for reporting and reproducing the bug and does
not require debugging information files to be installed.
The result is saved in the problem directory in a file named core_backtrace.
Integration with libreport events
abrt-action-generate-core-backtrace can be used as an analyzer for application crashes which dump core.
Example usage in report_event.conf:
EVENT=analyze analyzer=CCpp
abrt-action-generate-core-backtrace
OPTIONS
-d DIR
Path to problem directory.
-r
Do not hash function fingerprints. Useful for debugging.
-v
Be more verbose. Can be given multiple times.
AUTHORS
o ABRT team
abrt 2.1.11 06/18/2014 ABRT-ACTION-GENERA(1)