[Fedora-i18n-bugs] [Bug 594707] New: [abrt] crash in w3m-0.5.2-15.fc12: raise: Process /usr/bin/w3m was killed by signal 6 (SIGABRT)

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: [abrt] crash in w3m-0.5.2-15.fc12: raise: Process /usr/bin/w3m was killed by signal 6 (SIGABRT)

https://bugzilla.redhat.com/show_bug.cgi?id=594707

           Summary: [abrt] crash in w3m-0.5.2-15.fc12: raise: Process
                    /usr/bin/w3m was killed by signal 6 (SIGABRT)
           Product: Fedora
           Version: 12
          Platform: i686
        OS/Version: Linux
            Status: NEW
 Status Whiteboard: abrt_hash:d106ee41a2e44b3f3c0024b24e471d3fd09e8baa
          Severity: medium
          Priority: low
         Component: w3m
        AssignedTo: pnemade at redhat.com
        ReportedBy: theo148 at gmail.com
         QAContact: extras-qa at fedoraproject.org
                CC: pnemade at redhat.com, i18n-bugs at lists.fedoraproject.org
    Classification: Fedora


abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: w3m -o indent_incr=0 -o multicol=false -o no_cache=true -o
use_cookie=false -o display_charset=utf8 -o system_charset=utf8 -o
follow_locale=false -o use_language_tag=true -o ucs_conv=true -T text/html
-dump /home/antiaircraft/Archives/php-bigxhtml.html
comment: I'm pretty sure this crash happened when I moved a large HTML file
(the extracted single-page PHP manual) while Tracker was using w3m to index it.
I haven't been able to reproduce the crash however.
component: w3m
crash_function: raise
executable: /usr/bin/w3m
global_uuid: d106ee41a2e44b3f3c0024b24e471d3fd09e8baa
kernel: 2.6.32.12-115.fc12.i686
package: w3m-0.5.2-15.fc12
rating: 4
reason: Process /usr/bin/w3m was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.