Bug 600213 - [abrt] crash in firefox-3.6.3-4.fc13: Process /usr/lib/firefox-3.6/firefox was killed by signal 6 (SIGABRT)
[abrt] crash in firefox-3.6.3-4.fc13: Process /usr/lib/firefox-3.6/firefox wa...
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2010-06-04 03:21 EDT by yogeshp08
Modified: 2010-07-28 11:11 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-28 11:11:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (65.40 KB, text/plain)
2010-06-04 03:21 EDT, yogeshp08
no flags Details

  None (edit)
Description yogeshp08 2010-06-04 03:21:00 EDT
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/firefox-3.6/firefox ' http://localhost:9001//home/yogesh/.schrodinger/help/2009/maestro/load_python_api.html '
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib/firefox-3.6/firefox
global_uuid: d33e4a98d765b437867119f758b405f1a0970eee
package: firefox-3.6.3-4.fc13
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
Comment 1 yogeshp08 2010-06-04 03:21:02 EDT
Created attachment 421144 [details]
File: backtrace
Comment 2 d. johnson 2010-07-28 11:11:15 EDT
Unfortunately, it appears that you are loading some third party application:

0xb777e7d0  0xb77f8da4  Yes (*)     /home/yogesh/Programs/Schrodinger_Maestro/maestro-v90211/lib/Linux-x86/libstdc++.so.6

This application is using bundled libraries and does not have debuginfo.  You will need to contact them for support.

Thank you for taking the time to report this bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash, because there are no debugging symbols loaded (probably abrt failed to load them).

Unfortunately, we cannot use this backtrace.


Fedora Bugzappers volunteer triage team

Note You need to log in before you can comment on or make changes to this bug.