Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 586311 - [abrt] crash in firefox-3.6.3-4.fc13: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV) [NEEDINFO]
[abrt] crash in firefox-3.6.3-4.fc13: Process /usr/lib/firefox-3.6/firefox wa...
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
13
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
abrt_hash:84e85f86c6602e9d240fc34f1b1...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-04-27 05:35 EDT by csuwhm
Modified: 2010-05-01 00:08 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-01 00:08:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
campbecg: needinfo? (csuwhm)


Attachments (Terms of Use)
File: backtrace (49.06 KB, text/plain)
2010-04-27 05:35 EDT, csuwhm
no flags Details

  None (edit)
Description csuwhm 2010-04-27 05:35:41 EDT
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/firefox-3.6/firefox
component: firefox
executable: /usr/lib/firefox-3.6/firefox
global_uuid: 84e85f86c6602e9d240fc34f1b12a0782fbfea07
kernel: 2.6.33.2-57.fc13.i686.PAE
package: firefox-3.6.3-4.fc13
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 csuwhm 2010-04-27 05:35:43 EDT
Created attachment 409414 [details]
File: backtrace
Comment 2 Chris Campbell 2010-05-01 00:08:10 EDT
Bad or corrupted back-trace.


We will review this issue again once you've had a chance to attach this information.

Thank you very much in advance.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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