| Summary: | A MarkerUpdater is required for JSDT debug | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] JSDT | Reporter: | jdance | ||||
| Component: | Debug | Assignee: | Michael Rennie <Michael_Rennie> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Simon Kaegi <simon_kaegi> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | Michael_Rennie, thatnitind | ||||
| Version: | 3.2 | ||||||
| Target Milestone: | 3.3 M4 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 327019 | ||||||
| Attachments: |
|
||||||
|
Description
jdance
(In reply to comment #0) > > The main issue is that JSDT tries to restrict where breakpoints can be set. No, you just found a bug in our location verifier... > This scenario also happens when lines are shifted through editing the file, and > the breakpoint ends up on an invalid line. This is another bug: for the fact that we do not a have a marker updater. Changing the bug to reflect the need for a marker updater. Created attachment 183631 [details]
fix
The patch provides a marker updater for all markers that subclass the wst.jsdt.debug.marker type.
Also has a couple of performance fixes to leverage the shared AST from JSDT core instead of creating a new one to find breakpoint locations.
applied to HEAD |