Description of problem: Tried to report a crash on the JVM (openjdk), but at the final step, after logging into bugzilla and before trying to create the new bug, I got an assertion error and abrt crashed. I could not copy the assertion message in time. Version-Release number of selected component: libreport-plugin-bugzilla-2.2.3-2.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: reporter-bugzilla -b -c /etc/libreport/plugins/bugzilla.conf -F /etc/libreport/plugins/bugzilla_format.conf -A /etc/libreport/plugins/bugzilla_formatdup.conf crash_function: sr_stacktrace_free executable: /usr/bin/reporter-bugzilla kernel: 3.16.2-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #4 sr_stacktrace_free at generic_stacktrace.c:166 #5 append_short_backtrace at reporter-bugzilla.c:362 #6 append_item at reporter-bugzilla.c:406 #7 generate_bz_comment at reporter-bugzilla.c:494
Created attachment 940463 [details] File: backtrace
Created attachment 940464 [details] File: cgroup
Created attachment 940465 [details] File: core_backtrace
Created attachment 940466 [details] File: dso_list
Created attachment 940467 [details] File: environ
Created attachment 940468 [details] File: limits
Created attachment 940469 [details] File: maps
Created attachment 940470 [details] File: open_fds
Created attachment 940471 [details] File: proc_pid_status
Created attachment 940472 [details] File: var_log_messages
Thank you for taking the time to report this crash. The assertion message is included in the attached backtrace and denotes an impossible code execution path. Could you please try to report the JVM crash again and report the results here? If the crash is reproducible, please attach the data of the JVM crash that are stored in one of "/var/tmp/abrt/ccpp*" directories.
Hi and thanks for your replay. Unfortunately, I no longer have the JVM crash. I have tried to re-report the issue, but this time ABRT kept telling me that the crash is invalid, something about "invalid stacktrace", or along that line. After that, I have deleted the crash data. I hope the attached that of my report is enough to get you going in the good direction. Will try to report anything new that pops up in the meanwhile.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.