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: Process /usr/bin/w3m was killed by signal 11 (SIGSEGV)
https://bugzilla.redhat.com/show_bug.cgi?id=575752
Summary: [abrt] crash in w3m-0.5.2-15.fc12: Process /usr/bin/w3m was killed by signal 11 (SIGSEGV) Product: Fedora Version: 12 Platform: x86_64 OS/Version: Linux Status: NEW Status Whiteboard: abrt_hash:94f636b14840fae853fa53bf99ab456456010f28 Severity: medium Priority: low Component: w3m AssignedTo: pnemade@redhat.com ReportedBy: rbinkhor@redhat.com QAContact: extras-qa@fedoraproject.org CC: pnemade@redhat.com, fedora-i18n-bugs@redhat.com Estimated Hours: 0.0 Classification: Fedora Target Release: ---
abrt 1.0.8 detected a crash.
architecture: x86_64 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/rbinkhorst/buildroot/BUILD/xulrunner-1.9.0.10/mozilla/layout/generic/crashtests/323386-1.html comment: No idea, it popped up in ABRT component: w3m executable: /usr/bin/w3m kernel: 2.6.32.9-70.fc12.x86_64 package: w3m-0.5.2-15.fc12 rating: 4 reason: Process /usr/bin/w3m was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine)
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=575752
--- Comment #1 from Robert Binkhorst rbinkhor@redhat.com 2010-03-22 06:42:31 EDT --- Created an attachment (id=401694) --> (https://bugzilla.redhat.com/attachment.cgi?id=401694) File: backtrace
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=575752
Parag pnemade@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED
--- Comment #2 from Parag pnemade@redhat.com 2010-05-24 05:21:51 EDT --- Are you still able to reproduce this?
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=575752
--- Comment #3 from Robert Binkhorst rbinkhor@redhat.com 2010-05-25 04:32:57 EDT --- I've not seen it dump core again, but maybe I just didn't trigger it. As I'm unsure why it crashed on me it's hard to say whether it's resolved or not... I guess since no-one else has attached to this BZ and it's not happened again you can close it and it will re-open if it happens again.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=575752
--- Comment #4 from Parag pnemade@redhat.com 2010-05-25 04:37:24 EDT --- Actually few other people do found this bug but when asked them are you able to reproduce they said no.
So, it looks strange why it happened only once to all such bug reporters.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=575752
Parag pnemade@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |NOTABUG
i18n-bugs@lists.fedoraproject.org