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.
RC1 build #200610030000 of NetBeans 5.5 Windows XP, JDK 1.6.0 RC build #100 Description: ============ I understand this is most probably "as designed" but pretty confusing from user's point of view. When "Step Out" is used and the call stack ends in Java classes, the application looks like running normally but it only waits until appropriate user class will be called again. Then it stops on the last possible "step out" point. Steps to reproduce: =================== 1. Generate from template AnagramGame1 sample project. 2. Open "com.toy.anagrams.ui.About.java" class into editor. 3. Setup breakpoint at line 89 with setVisible(false); code. 4. Press F5 to debug the main project. 5. Once it's run, invoke "File|About" from menu and then press "Close" button. 6. When the breakpoint is hit, use "Run|Step Out" 4 times until the anagram game continues. 7. Now invoke "File|About" again but debugger stops unexpectedly at line 164 in AnagramGame.java class although there is no breakpoint there.
The debugger stops as a result of step out. Thus, according to smart-stepping rules, this behavior is O.K. But I understand that the behavior is unexpected and to our users it looks like a bug.
It's unvelivable, but this issue is almost identical to issue #54485. Both Jiri invented the same scenario. *** This issue has been marked as a duplicate of 54485 ***
Hm, verifying as duplicate. :-|