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.

Bug 145423 - Step into doesn't work. after code changes are applied
Summary: Step into doesn't work. after code changes are applied
Status: VERIFIED DUPLICATE of bug 145421
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-28 13:55 UTC by Peter Pis
Modified: 2008-09-04 16:01 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Pis 2008-08-28 13:55:04 UTC
Product Version: NetBeans IDE Dev (Build 200808280201)
Java: 1.6.0_10-rc; Java HotSpot(TM) Client VM 11.0-b15
System: Windows XP version 5.1 running on x86; Cp1252; en_GB (nb)
Userdir: D:\ide\65\user

Steps (see issue #145416 for source file):
1. Replace line "System.out.println..." with "X" and save the file.
2. Put bkpt on line where "run(i)" is being called.
3. Debug file.
4. Push "F8" - "Debugger stopped on uncompilable source code" message is printed in "Debugger Console".
5. Then correct the code. (System.out.println("");) and save the file.
6. Thread pops back to "run(i)" method.
7. Push "F7" (Step into) - Thread is stopped on the first line of the "run" method.
8. Push "F7" again - it steps back "for" statement.

User would expect to step through lines in "run" method while pushing "F7" in this case.
Comment 1 Martin Entlicher 2008-08-28 15:56:29 UTC
IMHO this is a duplicate of issue #145421.
This seems to be caused by steps submitted during smart-stepping.

If I enable debugging in JDK sources and use SHIFT-F7, I can step through System.out.println(""); and continue on next
lines. It seems like any "Step Over" issued inside System.out.println(""); call just resumes the thread - this is what
issue #145421 is about.

*** This issue has been marked as a duplicate of 145421 ***
Comment 2 Peter Pis 2008-09-04 16:01:36 UTC
Verified. Dup.