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 145421 - Step over doesn't work after code changes are applied
Summary: Step over doesn't work after code changes are applied
Status: VERIFIED WONTFIX
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords:
: 145423 (view as bug list)
Depends on:
Blocks: 144703
  Show dependency tree
 
Reported: 2008-08-28 13:47 UTC by Peter Pis
Modified: 2013-02-13 16:03 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Pis 2008-08-28 13:47:24 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. Main thread pops back to "run(i)" method.
7. Now push "F8" several times - it should go through the each line in "for" statement.

But it acts like a resume that is wrong.
Comment 1 Martin Entlicher 2008-08-28 15:34:14 UTC 
I do not think we'll be able to fix this. Step event is not received, bug is in JDK, defect
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6742507 submitted.
Comment 2 Martin Entlicher 2008-08-28 15:56:24 UTC 
*** Issue 145423 has been marked as a duplicate of this issue. ***
Comment 3 Martin Entlicher 2008-09-04 16:43:50 UTC 
Since I can not fix that from NetBeans (it's a JDK defect), I'll remove the automatic application of code changes on
save in compile-on-save mode. This functionality will be available via the "Apply Code Changes" action only as it is in
past releases.
This will reduce the chance that users will run into this issue.
After http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6742507 is fixed and class reload does not cause critical
issues, we can return the automatic mode back.

After that change is done, I'll resolve this issue as WONTFIX.
Comment 4 Martin Entlicher 2008-09-05 18:11:02 UTC 
The automatic application of code changes in compile-on-save removed in changeset:   100349:5cf08a0df992
"Apply Code Changes" action is enabled if there are some changes to apply.

System property "debugger.apply-code-changes.on-save" introduced to turn the automatic application of code changes on. Use
-J-Ddebugger.apply-code-changes.on-save=true
switch if you want that.

Resolving as wontfix, since this issue is not fixable in NetBeans. Just the probability that users will encounter that
is (hopefully) reduced.

http://hg.netbeans.org/main/rev/5cf08a0df992
Comment 5 Quality Engineering 2008-09-06 05:22:02 UTC 
Integrated into 'main-golden', will be available in build *200809060201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/5cf08a0df992
User: mentlicher@netbeans.org
Log: #145421 - Automatic application of code changes in compile-on-save mode disabled.
System property debugger.apply-code-changes.on-save added to enable that functionality back.
Comment 6 Peter Pis 2008-09-12 15:03:04 UTC 
Verified.
Comment 7 Petr Jiricka 2013-02-13 16:03:59 UTC 
Looks like the JDK issue was duplicated to http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6782740