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 LINUX
ubuntu-bug
apport-bug(1) General Commands Manual apport-bug(1)
NAME
apport-bug, apport-collect - file a bug report using Apport, or update an existing report
SYNOPSIS
apport-bug
apport-bug symptom | pid | package | program path | .apport/.crash file
apport-collect report-number
DESCRIPTION
apport-bug reports problems to your distribution's bug tracking system, using Apport to collect a lot of local information about your sys-
tem to help the developers to fix the problem and avoid unnecessary question/answer turnarounds.
You should always start with running apport-bug without arguments, which will present a list of known symptoms. This will generate the most
useful bug reports.
If there is no matching symptom, you need to determine the affected program or package yourself. You can provide a package name or program
name to apport-bug, e. g.:
apport-bug firefox
apport-bug /usr/bin/unzip
In order to add more information to the bug report that could help the developers to fix the problem, you can also specify a process ID
instead:
$ pidof gnome-terminal
5139
$ apport-bug 5139
As a special case, to report a bug against the Linux kernel, you do not need to use the full package name (such as linux-
image-2.6.28-4-generic); you can just use
apport-bug linux
to report a bug against the currently running kernel.
Finally, you can use this program to report a previously stored crash or bug report:
apport-bug /var/crash/_bin_bash.1000.crash
apport-bug /tmp/apport.firefox.332G9t.apport
Bug reports can be written to a file by using the --save option or by using apport-cli.
apport-bug detects whether KDE or Gnome is running and calls apport-gtk or apport-kde accordingly. If neither is available, or the session
does not run under X11, it calls apport-cli for a command-line client.
UPDATING EXISTING REPORTS
apport-collect collects the same information as apport-bug, but adds it to an already reported problem you have submitted. This is useful
if the report was not originally filed through Apport, and the developers ask you to attach information from your system.
OPTIONS
Please see the apport-cli(1) manpage for possible options.
ENVIRONMENT
APPORT_IGNORE_OBSOLETE_PACKAGES
Apport refuses to create bug reports if the package or any dependency is not current. If this environment variable is set, this
check is waived. Experts who will thoroughly check the situation before filing a bug report can define this in their ~/.bashrc or
temporarily on the command line when calling apport-bug.
SEE ALSO
apport-cli(1)
AUTHOR
apport and the accompanying tools are developed by Martin Pitt <martin.pitt@ubuntu.com>.
Martin Pitt September 08, 2009 apport-bug(1)