Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 323288 - debugger; statement line locations are completely bogus
Summary: debugger; statement line locations are completely bogus
Status: CLOSED DUPLICATE of bug 308357
Alias: None
Product: JSDT
Classification: WebTools
Component: Debug (show other bugs)
Version: 3.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Simon Kaegi CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-20 15:08 EDT by Michael Rennie CLA
Modified: 2010-09-28 13:48 EDT (History)
1 user (show)

See Also:

Attachments
screen shot (45.94 KB, image/png)
2010-08-20 15:08 EDT, Michael Rennie CLA 		no flags Details
View All 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 Michael Rennie CLA 2010-08-20 15:08:52 EDT 
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.
Comment 1 Michael Rennie CLA 2010-09-28 13:48:07 EDT 

*** This bug has been marked as a duplicate of bug 308357 ***