Bug 555644 - [abrt] crash in firefox-3.5.6-1.fc12
[abrt] crash in firefox-3.5.6-1.fc12
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-01-14 23:24 EST by William Zhou
Modified: 2010-04-09 22:01 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-04-09 22:01:07 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 (39.43 KB, text/plain)
2010-01-14 23:24 EST, William Zhou
no flags Details

  None (edit)
Description William Zhou 2010-01-14 23:24:02 EST
abrt 1.0.3 detected a crash.

Attached file: backtrace
cmdline: /usr/lib/firefox-3.5.6/firefox
component: firefox
executable: /usr/lib/firefox-3.5.6/firefox
package: firefox-3.5.6-1.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
Comment 1 William Zhou 2010-01-14 23:24:06 EST
Created attachment 384515 [details]
File: backtrace
Comment 2 Chris Campbell 2010-01-15 09:22:03 EST
#3  <signal handler called>
No symbol table info available.
#4  0x00152afe in _IO_vfprintf_internal (s=<value optimized out>, 
    format=<value optimized out>, ap=<value optimized out>) at vfprintf.c:1593
#5  0x00203d52 in __vasprintf_chk (result_ptr=<value optimized out>, 
    flags=<value optimized out>, format=<value optimized out>, 
    args=<value optimized out>) at vasprintf_chk.c:68
#6  0x00a7d264 in vasprintf (__ap=<value optimized out>, 
    __fmt=<value optimized out>, __ptr=0xbff6185c)
    at /usr/include/bits/stdio2.h:199
No locals.
#7  IA__g_vasprintf (__ap=<value optimized out>, __fmt=<value optimized out>, 
    __ptr=0xbff6185c) at gprintf.c:315
        len = <value optimized out>
        __PRETTY_FUNCTION__ = "IA__g_vasprintf"
#8  0x00a68ac7 in IA__g_strdup_vprintf (format=<value optimized out>, 
    args=<value optimized out>) at gstrfuncs.c:244
        string = 0x0
#9  0x00a50022 in IA__g_logv (log_domain=<value optimized out>, 
    log_level=<value optimized out>, format=<value optimized out>, 
    args1=<value optimized out>) at gmessages.c:516

Fedora Bugzappers volunteer triage team
Comment 3 Chris Campbell 2010-01-15 09:26:21 EST
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

First of all, could we get output of the command, saved in a text file and attached to this bug:

$ rpm -qa *xulrun* *firefox* *mozilla* *flash* *plugin*

Please also install debuginfo for Firefox.

# debuginfo-install firefox

Then run firefox inside the gdb debugger. Please do the following:

$ firefox -g

Stuff will appear. Ignore this until you get the gdb command prompt, then do:

(gdb) run

Now, firefox should start up. Use it and reproduce the crash. When firefox crashes, you should be back to the gdb prompt. Now do:

(gdb) thread apply all backtrace

More screens of stuff will occur. Copy all of this part to your editor of choice, such as gedit, and save it as an uncompressed file and attach it to this bug report.

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

Thanks in advance, for your extra efforts.

Fedora Bugzappers volunteer triage team
Comment 4 Matěj Cepl 2010-02-26 07:19:03 EST
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
Comment 5 Chris Campbell 2010-04-09 22:01:07 EDT
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.


Fedora Bugzappers volunteer triage team

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