Bugzilla – Full Text Bug Listing
| Summary: | debugger; statement line locations are completely bogus | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] JSDT | Reporter: | Michael Rennie <Michael_Rennie> | ||||
| Component: | Debug | Assignee: | Project Inbox <jsdt.debug-inbox> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Simon Kaegi <simon_kaegi> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | thatnitind | ||||
| Version: | 3.2 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
*** This bug has been marked as a duplicate of bug 308357 *** |
Created attachment 177135 [details] screen shot code from HEAD When the debugger suspends on a debugger; statement, the Rhino interpreter reports a bogus location. We need to investigate tracking the line locations to match it to the correct debugger; statement - I'm not even sure we can do this looking at the hooks Rhino gives us... The attached screen shot shows the debugger stopped on the the second debugger; statement, but the instruction pointer + stackframe adornment is completely wrong. I know it is on the second debugger statement because I was tracing the event queue, and it is suspended on the second debugger; statement event from Rhino.