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 193532 - [70cat][debugger] Debugger does not clean up Current Processing Location when debugger is terminated.
Summary: [70cat][debugger] Debugger does not clean up Current Processing Location when...
Status: RESOLVED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 7.0
Hardware: All All
: P4 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2010-12-17 08:46 UTC by esmithbss
Modified: 2015-09-04 13:13 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Screen Capture showing no execution, debugger, but still showing current execution point. (2.93 MB, image/bmp)
2010-12-17 08:53 UTC, esmithbss 		Details
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 esmithbss 2010-12-17 08:46:21 UTC 
Product Version = NetBeans IDE Dev (Build 201012150001)
Operating System = Windows XP version 5.1 running on x86
Java; VM; Vendor = 1.6.0_22
Runtime = Java HotSpot(TM) Client VM 17.1-b03

When running a JUnit test with an abstract superclass (on the JUnit 4 test class), and debugging a recursive public static method in the Abstract superclass, terminating the JUnit execution does not clean up the Current Execution Position from the Editor.
Comment 1 esmithbss 2010-12-17 08:53:02 UTC 
Created attachment 104189 [details]
Screen Capture showing no execution, debugger, but still showing current execution point.
Comment 2 Martin Entlicher 2010-12-20 16:56:37 UTC 
I was not able to reproduce this.
IMHO this is a rare random issue.
Comment 3 Martin Entlicher 2015-09-04 13:13:47 UTC 
While I've seen in the past staled or incompletely painted annotations, I did not see this recently. Thus IMHO this was already fixed by other changes.