Zen

Source string Source string

(The following assumes Gnome as the desktop ... someone else will have to update for KDE/Others)
96/10000 · 96

The string is read-only.

English Actions
If the program that crashes leaves a core dump, you can use GDB to obtain a stack trace. Core dumps are saved in a file on your hard disk and are usually named something along the lines of "core" or "core.3124". To obtain a stack trace from one of these files, run the following command:
gdb name-of-program core-file-name
Where `name-of-program` is the name of the program that crashed (for example: /usr/bin/gnome-panel), and `core-file-name` is the name of the core file that contains the core dump (for example: core.7812).
If that does not work (meaning that you don't get any output--this may be the case in programs which are not multi-threaded), type `bt` instead. If you still do not have any output, read <<special,this note>> about obtaining a stack trace under special circumstances. The output is the stack trace. Cut and paste all of it into a text file.
Note that creation of core files is disabled in Fedora by default (in /etc/profile). To enable them for a shell session, type at the shell prompt:
ulimit -c unlimited
How to install ABRT
If you installed Fedora via a LiveCD image, ABRT should already be installed. You should be able to start it in `Applications -> System Tools -> Automatic Bug Reporting Tool`. If ABRT is not installed, for whatever reason, you can install it manually by doing the following on a command line:
$ su -c 'dnf install abrt'
or go to `System` -> `Administration` -> `Add/Remove Software` in Gnome, and type`abrt` in the search box and select `Find`. Select the abrt package and apply the changes.
Configuring ABRT for Bugzilla
Go to `Application` -> `System Tools` -> `Automated Bug Reporting Tool` and select it to start it manually. Once the GUI window appears, choose `Edit` -> `Plugins` and from the Settings window, scroll down, highlight Bugzilla and choose `Configure Plugin`. The Bugzilla URL should be https://bugzilla.redhat.com[https://bugzilla.redhat.com] and enter your own Bugzilla login and password in the proper boxes.
If you do not yet have a Bugzilla account, now is the time to get one, just go to the URL as displayed on that page and https://bugzilla.redhat.com/createaccount.cgi[create a new account].
Next time you have a program crash, and ABRT triggers, when you hit Report, ABRT will be able to automatically log in to Bugzilla and submit a Bug Report for you.
Using ABRT
(The following assumes Gnome as the desktop ... someone else will have to update for KDE/Others)
If ABRT detects a crashed program, you will get an ABRT alert. This will be visually indicated by a flashing red light in the system tray. Left click on the alert light, and the Automatic Bug Reporting Tool should start, displaying all of the crashes it has registered. To report the bug, right click on it and choose report. ABRT will gather the logs it needs to submit with the bug and will then let you know it is going to submit a bug on your behalf. If you have configured ABRT as in the previous section, it will then ask you to verify whether or not to include the various logs, then will automatically go out to Bugzilla and open a bug, attaching the logs into the bug. It will then show you the bug number so that you can track the bug as it is worked on.
Configuring ABRT when missing Debuginfos
When you right click on a bug in ABRT and choose Report, ABRT will attempt to go out and retrieve the logs it will need to send as part of the bug report. The developers have added code to detect whether or not symbolic traces are included within the backtrace, and if it detects that there are none, ABRT will alert you of this, and will show you the command to run. This is the same as what is shown in the <<debuginfo,debuginfo>> section.
Special cases
Programs running as another user
If you do not get any output from gdb after typing `thread apply all bt` or `bt`, it may be because the program is run as root or as another user. In GNOME for example, this is the case when running gnome-games. In such cases, you will need to be root in order to capture a trace. So, quit gdb, login as root, and then repeat the steps to obtain a stack trace.
Firefox
Install Firefox and Xulrunner debug info packages - run `ebuginfo-install firefox xulrunner` as root on the command line.
Run `firefox -g` on the command line. That will start firefox running inside of gdb debugger.
In gdb, you should see gdb prompt `(gdb)`. Issue the command `run -safe-mode`. A dialog window will pop up, disable all add-ons here and continue in safe mode.
Do whatever is necessary to make firefox crash and follow the instructions above for gdb usage.
When Firefox crashes, <<gdb,obtain the backtrace>> and attach it to bugzilla.
For additional info see xref:troubleshooting-mozilla-products.adoc[Debugging guidelines for Mozilla products].
Thunderbird
It's almost the same as for Firefox, just the debug info packages are different. Install them by "debuginfo-install thunderbird" command as root on the console.

Loading…

User avatar None

String updated in the repository
(The following assumes Gnome as the desktop ... someone else will have to update for KDE/Others)
(The following assumes Gnome as the desktop ... someone else will have to update for KDE/Others)
a year ago
Browse all string changes

Things to check

Ellipsis 1

The string uses three dots (...) instead of an ellipsis character (…)

Reset

Glossary

English English
No related strings found in the glossary.

16700934 String information

Source string description
type: Plain text
Flags
read-only
Source string location
./pages/bugzilla-providing-a-stacktrace.adoc:266
String age
a year ago
Last updated
a year ago
Source string age
a year ago
Translation file
pot/master/pages/bugzilla-providing-a-stacktrace.pot, string 96