Created attachment 944003 [details] core backtrace Description of problem: I don't know what caused the crash. I tried to start MediathekView.jar from http://zdfmediathk.sourceforge.net/ (running from source). Afaik this application contains no native code so there should this crash might be triggered but not caused by zdfmediathk. Version-Release number of selected component (if applicable): java-1.8.0-openjdk-headless-1.8.0.20-12.b26.fc21 from F21 alpha How reproducible: doesn't seem to be reliably reproducible. Additional info: ABRT failed to report the bug automatically so I am doing it manually. cmdline: java -Xms256M -Xmx1G -jar /home/christian/.local/src/JAVA/zdfmediathk-code/dist/MediathekView.jar executable: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.20-12.b26.fc21.x86_64/jre/bin/java kernel: 3.16.3-302.fc21.x86_64 uid: 1000
Created attachment 944004 [details] cgroup
Created attachment 944005 [details] dso_list
Created attachment 944006 [details] environ
Created attachment 944007 [details] limits
Created attachment 944008 [details] maps
Created attachment 944009 [details] open_fds
Created attachment 944010 [details] proc_pid_status
from var_log_messages: [System Logs]: Okt 04 18:06:24 chstpc-2 abrt-hook-ccpp[18114]: Saved core dump of pid 21793 (/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.20-12.b26.fc21.x86_64/jre/bin/java) to /var/tmp/abrt/ccpp-2014-10-04-18:06:21-21793 (740499456 bytes) Okt 05 02:15:06 chstpc-2 kernel: traps: java[5108] trap int3 ip:7f2b3fbf4051 sp:7f2b189f85a8 error:0 Okt 05 02:15:08 chstpc-2 abrt-hook-ccpp[5417]: Saved core dump of pid 5097 (/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.20-12.b26.fc21.x86_64/jre/bin/java) to /var/tmp/abrt/ccpp-2014-10-05-02:15:06-5097 (486436864 bytes)
Hi Christian, thank you for taking the time to report this crash and sorry for the troubles with ABRT. It could be also useful to provide a GDB backtrace. If you still have the crash data directory on your disk, go to that directory, run 'abrt-action-perform-ccpp-analysis' and attach 'backtrace' file here.
Created attachment 944169 [details] backtrace as requested in #8 Seems like abrt-action-perform-ccpp-analysis was missing yum which caused the crash.
Hi Christian, so I am a bit unclear -- is everything working now, or is comment #10 only referring to inability to generate a backtrace?
comment #10 refers to the backtrace, see abrt bug reported separately in https://bugzilla.redhat.com/show_bug.cgi?id=1148207 . The backtrace is the one from java crash. I didn't run into this java bug any more (in case your comment is the same as in the other bug I reported), it happened only once.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.