This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
dev build 20030534300100 Innotek JDK 1.4.1_02 There is a known bug which prevents JPDA from working within Netbeans under OS/2. There is a high probability this is a bug in the JDK port itself but seeing as Netbeans is a huge framework the guys doing the port are having a very difficult time trying to track down the problem. The symptoms are: - We open Netbeans, go to the the sample source and select Debug - Step into. - It will start to launch a 2nd JVM in debug mode but it will never arrive at the source code position (i.e. the 2nd VM gets stuck). - When terminating Netbeans, the 2nd VM will continue to run and the debuggee will start. I would flag this bug as P1 (due to its importance) but seeing as this is probably a JVM bug and is limited to a single platform (OS/2) I will leave it as P2 for now. Is there anything you can do on your end to help us track down this problem? Perhaps there is some debugging output you could enable or something which would help us track down where the debugging session is getting stuck? Do you perhaps have a smaller testcase which you use for nightly tests of the Netbeans JPDA module we could use? Your help is greatly appreciated! Thanks, Gili
Hi Gili, does this mean that it was not possible to reproduce the bug using "jdb" debugger? If you have not tested it using "jdb", I would recommend you to do so. If you can reproduce it using "jdb", it is nearly sure that the problem is in the JVM, and you would have the necessary small testcase. Otherwise the question is open. (If necessary, I think I could give you a small testing application for JDI, but if it is not reproducible using "jdb" I do not think it will help you.)
JDB works just fine. JSWAT works fine too.
Hanz, there are some debugs to track communication with JDI. Could you list some of these here, please, they may help.
We have only -J-Dnetbeans.debug.step=true netbeans.debug.smartSteppingInfo but they will probabaly not hepl in this situation. You should debug debugger code. And what about attaching, does it work? And Start Debugging works (in place of Step Into)?
What do "-J-Dnetbeans.debug.step=true" and "netbeans.debug.smartSteppingInfo" do? Debugging the Netbeans debugger is probably not an option as its it too complex. We need a minimal testcase (like nightly QA tests) to track down the problem. Both Debug | Attach and Debug | Start Debugging Session do not work; they both hang.
Adding keyword JDK_SPECIFIC since we haven't seen it on any other JDK or OS. Hanz, would you provide info about what those special arguments do? Thanks
I am adding the keword INCOMPLETE as we do not have enough information to evaluate it. Switches Hanz mentioned just print some trace information to the console but are not JDI-specific enough to track down the problem. You may try them. I suggest we either set up an OS/2 box and test it there or somebody debug the netbeans debugger on OS/2 and provide patch/fix/hints.
I've actually given up on JDK 1.4.1 on OS/2. Due to an OS-architecture limitation (one graphic-drawing thread for the entire OS, not one per application) the people who ported the JDK found it impossible to debug a Java application on the same machine as it was being run on. As such, I've actually jumped ship to Windows and am no longer the supporter of Netbeans under OS/2. If someone wants to follow-up on this issue, simply download and install the latest JDK from here: http://www.innotek.de/products/javaos2/javaos2general_e.html Otherwise, please close this issue as WON'T FIX. Sorry :(
Looks like problem of JDK. I do not have enough information to help you. Logging of jdi communication is not supported and its not easy thing to do - in fact its feature not a bug and we do not have resources to do it.
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.