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.
See attached project and NB settings. - Set breakpoint on 1st executable line in main() of test.java.nio.BufferUtilsTest - Start debugger on test.java.nio.BufferUtilsTest - 3 times invoke "Step Into" - Invoke "Step Over" (see attached screen shot) Instead of stepping to the next line the debugger continues to the end.
Created attachment 60708 [details] Project tree
Created attachment 60709 [details] NB settings
Created attachment 60710 [details] Screen shot before "Step Over"
Debugging this project by my 6.1 RC2 is a real nightmare ... Also "Run to Cursor" doesn't work. The only function, which works is "Step Into", so I have to step into each method and superclass even 'Object' to perform a debugger session. So for me 6.1 is not ready for shipping! :-(
On Linux this works fine for me in dev builds. Needs to be tested on Windows...
Jirka, could you please look at this ? Thanks in advance.
Can you please elaborate on what do you mean by "debugger continues to the end"? It works fine for us, Step Over from ByteBuffer.java:259 goes to ByteBuffer.java:1359 where a field is initialized. Where does it go for you? Run To Cursor works also fine for me. Do you have this "Java" project set as main? Run To Cursor executes the main project (if there's no debugging session) and sets a hidden breakpoint on the line with cursor.
I tried to debug your project and everything works fine (Step In/Out, Step Over). Product Version: NetBeans IDE 6.1 RC2 (Build 200804170002) Java: 1.5.0_13; Java HotSpot(TM) Client VM 1.5.0_13-b05 "Run to cursor" runs on main project. Check the ide help for more informations please (Java Applications > Debugging Applications > Debugging Sessions > Starting a Local Debugging Session).
By "debugger continues to the end" I mean, that there is _no_ stop (e.g. ByteBuffer.java:1359) until the entire run has terminated. Yes, project is set as main. Now I have a new similar problem: Debugger ignores Breakpoint. See attachments ...
I experienced a new problem too.
Created attachment 60744 [details] Debugger ignores Breakpoint
Created attachment 60745 [details] Changed project tree
Created attachment 60746 [details] Source Root / Filter for debugging
Product Version: NetBeans IDE 6.1 RC2 (Build 200804170002) Java: 1.6.0_06; Java HotSpot(TM) Client VM 10.0-b22 System: Windows XP version 5.1 running on x86; Cp1252; de_DE (nb) Userdir: C:\Dokumente und Einstellungen\ich\.netbeans\6.1rc2
Created attachment 60747 [details] messages.log + uigestures
See also: http://statistics.netbeans.org/analytics/detail.do?id=39462
From the message.log file it's apparent that debugger is crippled by NPE: java.lang.NullPointerException at java.util.StringTokenizer.<init>(StringTokenizer.java:182) at java.util.StringTokenizer.<init>(StringTokenizer.java:204) at org.netbeans.modules.java.j2seplatform.platformdefinition.Util.createClassPath(Util.java:68) at org.netbeans.modules.java.j2seplatform.platformdefinition.J2SEPlatformImpl.getStandardLibraries(J2SEPlatformImpl.java:232) at org.netbeans.modules.java.platform.classpath.PlatformClassPathProvider.findClassPath(PlatformClassPathProvider.java:80) at org.netbeans.api.java.classpath.ClassPath.getClassPath(ClassPath.java:538) at org.netbeans.api.java.source.ClasspathInfo.create(ClasspathInfo.java:163) at org.netbeans.api.java.source.ClasspathInfo.create(ClasspathInfo.java:183) at org.netbeans.api.java.source.JavaSource.forFileObject(JavaSource.java:473)
BTW, What is JDK_1.6.0-b105_debug ? Where did you download this JDK from? Or have you built it yourself?
It's just a descriptor for original JDK 1.6.0-b105 distribution + sources from j2se\src e.g. sun.nio.cs. Another reason for not using the default platform is described here: Issue 130352 ... and here (Sources for JDK 1.6.0_06 aren't available yet): https://java-net.dev.java.net/issues/show_bug.cgi?id=418
It is caused by strange configuration of J2SEPlatform. getSystemProperties().get(SYSPROP_JAVA_CLASS_PATH) returned null
Fixed by: 6e77322db578
Well done. :-) Is it possible to have this fix in the next update for NB 6.1?