Description of problem: The abrt-java-connector agent, which is automatically added to the java runtime parameters by the shell script /usr/bin/java, interferes with the JDWP agent used for debugging. This prevents BlueJ from working properly, and should also affect any other debuggee started via /usr/bin/java. Version-Release number of selected component (if applicable): Name : abrt-java-connector Arch : x86_64 Epoch : 0 Version : 1.0.9 Release : 1.fc20 How reproducible: Always Steps to Reproduce: 1. Download BlueJ from http://bluej.org/download/files/bluej-311.jar 2. Run `java -jar bluej-311.jar` and "install" 3. Start BlueJ via the provided script 4. Create a new project 5. An error message appears: BlueJ cannot attach its debugger Alternatively, run any java application with: java -agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005 SomeApp and try to attach a debugger. Comment out the relevant lines in /usr/bin/java and JDWP will work. Actual results: Debugger cannot attach to JVM Expected results: Debugger works Additional info:
Thank you for the report! I've verified that BlueJ doesn't work properly but jdb works fine. See the following test output: $ java -agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005 ReadLine Listening for transport dt_socket at address: 5005 Hello, what's your name? > Jakub Bye bye Jakub! Exception in thread "main" java.lang.NullPointerException at ReadLine.main(ReadLine.java:22) ABRT problem creation: 'success' $ $ jdb -attach jdb -attach 127.0.0.1:5005 Set uncaught java.lang.Throwable Set deferred uncaught java.lang.Throwable Initializing jdb ... > VM Started: No frames on the current call stack main[1] run > Exception occurred: java.lang.NullPointerException (uncaught)"thread=main", ReadLine.main(), line=22 bci=103 main[1] cont > The application exited $ Hence I would not say that other debuggers are affected. Now, I'm trying to figure out the difference between starting Java from BlueJ and command line. I can see that BlueJ starts java without 'server=y' parameter.
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.