Description of problem: I've seen 2 native code crashes in java recently and both could not be reported using ABRT: https://bugzilla.redhat.com/show_bug.cgi?id=1149463 https://bugzilla.redhat.com/show_bug.cgi?id=1149473 Version-Release number of selected component (if applicable): abrt 2.2.2-9.fc21 How reproducible: Don't know. java crashes don't happen that much. Actual results: abrt was unable to report the bugs. Expected results: abrt should be able to report the bugs. Additional info: the event_log file has the full error message. It is the same for both bugs (ignoring the timestamp): 2014-10-04-18:06:36> Der Server hat mit einer Fehlermeldung geantwortet: »Validation failed: Element 'stacktrace' is invalid: List element is invalid: Element 'frames' is invalid: List element is invalid: Element 'file_name' is missing« 2014-10-04-18:06:36 reporter-ureport failed with exit code 1 2014-10-04-18:06:36* (»report_uReport« abgebrochen durch 1) 2014-10-04-18:06:48> Der Server hat mit einer Fehlermeldung geantwortet: »Validation failed: Element 'stacktrace' is invalid: List element is invalid: Element 'frames' is invalid: List element is invalid: Element 'file_name' is missing« 2014-10-04-18:06:48 reporter-ureport failed with exit code 1 2014-10-04-18:06:48* (»report_uReport« abgebrochen durch 1)
Hello, thank you for taking the time report this issue. This bug report should be filed against ABRT Server (http://retrace.fedoraproject.org/) but there is no such a component in Bugzilla yet. At first glance, it appears that we can safely ignore the last invalid frame in a core backtrace.
Could it be possible that this bug is a result of https://bugzilla.redhat.com/show_bug.cgi?id=1148207 ? If yes this bug could be closed.
(In reply to Christian Stadelmann from comment #2) > Could it be possible that this bug is a result of > https://bugzilla.redhat.com/show_bug.cgi?id=1148207 ? If yes this bug could > be closed. Thanks! Good point, but no, this bug is caused by something else. Our algorithm based on elfutils produced a backtrace where some of the function frames misses source file name and function name.
https://github.com/abrt/faf/pull/288 fixes this bug. It should get through the deployment process to our production server within a week. Thank you for reporting this issue.
gnome-abrt-1.0.0-1.fc21,abrt-2.3.0-2.fc21,libreport-2.3.0-2.fc21,satyr-0.15-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/gnome-abrt-1.0.0-1.fc21,abrt-2.3.0-2.fc21,libreport-2.3.0-2.fc21,satyr-0.15-1.fc21
*** Bug 1152663 has been marked as a duplicate of this bug. ***
Package gnome-abrt-1.0.0-1.fc21, abrt-2.3.0-2.fc21, libreport-2.3.0-2.fc21, satyr-0.15-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gnome-abrt-1.0.0-1.fc21 abrt-2.3.0-2.fc21 libreport-2.3.0-2.fc21 satyr-0.15-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-12856/gnome-abrt-1.0.0-1.fc21,abrt-2.3.0-2.fc21,libreport-2.3.0-2.fc21,satyr-0.15-1.fc21 then log in and leave karma (feedback).
I can configm the fix. Thanks!
gnome-abrt-1.0.0-1.fc21, abrt-2.3.0-2.fc21, libreport-2.3.0-2.fc21, satyr-0.15-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.