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)
Created attachment 401694 [details] File: backtrace
Are you still able to reproduce this?
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.
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.