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.
[ BUILD # : 201402150001 ] [ JDK VERSION : 1.7.0_45 ] STEPS: execute Two top level classes in one file - step functionality Test Case http://services.netbeans.org/synergy/client/app/index.html#/case/1227/suite/1664 /v/1 ACTUAL: debugger steps into method doIt directly skipping constructor. EXPECTED: debugger steps into constructor first and then method as per test case expected results. Most probably the test case should be updated to reflect the actual behavior, since it's also working the same way in 7.4 and you can enter the constructor if you explicitly select it.
The debugger does not step into the constructor even if the constructor has some dummy logic: public ClazzTwo() { int x = 0; } So now we have the fundamental question - is it expected that the debugger will step into the constructor at all (so there is a bug) or not (and then test spec should be adjusted)? Product Version: NetBeans IDE 8.1 Beta (Build 201507231027) Java: 1.8.0_60-ea; Java HotSpot(TM) 64-Bit Server VM 25.60-b23 Runtime: Java(TM) SE Runtime Environment 1.8.0_60-ea-b25 System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb) User directory: C:\Users\cendrowiczm\AppData\Roaming\NetBeans\8.1beta Cache directory: C:\Users\cendrowiczm\AppData\Local\NetBeans\Cache\8.1beta
It looks like the test specification was written when Step Into behaved in a simple way (like current Debug -> Step Into Next Method (SHIFT-F7)). Now you can choose where to step into. By default, the last method call is suggested. If you choose to step into the constructor, you will step there. The test spec. should be updated to reflect that.
Test specification updated accordingly. Thanks for your report.