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 267433 - Formatting code while actively debugging causes glitches in debugger highlightings
Summary: Formatting code while actively debugging causes glitches in debugger highligh...
Status: STARTED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 8.1
Hardware: PC Windows 10
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-04 16:52 UTC by ytn01
Modified: 2016-09-01 11:18 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 ytn01 2016-08-04 16:52:14 UTC
Product Version = NetBeans IDE Dev (Build 201607260002)
Operating System = Windows 10 version 10.0 running on amd64
Java; VM; Vendor = 1.8.0_102
Runtime = Java HotSpot(TM) 64-Bit Server VM 25.102-b14

Reproducibility: Happens every time

STEPS:
  * Add some breakpoints in your code and Debug run a java file or project (manually format the code to mismatch the format settings you have configured for your source files)
  * when breakpoint is hit in a method (preferably somewhere in the middle of a large method, with plenty of code with blocks), select the entire body of the method and format the method (alt+shift+F in windows)
  * format of the methods body will change to the code format setting you have in your preferences

ACTUAL:
  *  you will notice debugger hight marks will be out of place then after , especially as you step through expressions

EXPECTED:
  * debugger highlightings and markers should continue functioning righ
Comment 1 Martin Entlicher 2016-08-12 17:24:42 UTC
Reproduced.
Comment 2 Martin Entlicher 2016-09-01 11:18:06 UTC
The code freeze for 8.2 is approaching, this will be fixed in an update or in the next version.
Doing reformat during debugging is a rare use-case, moving to P3.