Bug 697929 - [abrt] firefox-3.6.16-1.fc14: __libc_start_main: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.6.16-1.fc14: __libc_start_main: Process /usr/lib/firefox-3.6...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3f7b5af695485f6723f09f5163f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-19 16:51 UTC by Michael Gruys
Modified: 2011-12-07 13:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-07 13:23:23 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (14.22 KB, text/plain)
2011-04-19 16:51 UTC, Michael Gruys 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Michael Gruys 2011-04-19 16:51:05 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 14563 bytes
cmdline: /usr/lib/firefox-3.6/firefox -UILocale nl
component: firefox
Attached file: coredump, 127369216 bytes
crash_function: __libc_start_main
executable: /usr/lib/firefox-3.6/firefox
kernel: 2.6.35.12-88.fc14.i686.PAE
package: firefox-3.6.16-1.fc14
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1303230793
uid: 500

How to reproduce
-----
1.open terminal
2.firefox
3.crash occurs
Comment 1 Michael Gruys 2011-04-19 16:51:08 UTC 
Created attachment 493229 [details]
File: backtrace
Comment 2 Martin Stransky 2011-12-07 13:23:23 UTC 
We're using mozilla crash reporter now, ABRT is no more used for Firefox/Thunderbird. If you can reliably reproduce the crash (you have a testcase, reproduction steps, etc.) please reopen the bug and attach the reproduction info and assign it directly to me (stransky).

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