Bug 327816 - Run to line hits breakpoints even with the platform setting to skip them turned on
Summary: Run to line hits breakpoints even with the platform setting to skip them turn...
Status: NEW
Alias: None
Product: JSDT
Classification: WebTools
Component: Debug (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: Future   Edit
Assignee: Project Inbox CLA
QA Contact: Simon Kaegi CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-14 14:29 EDT by Michael Rennie CLA
Modified: 2012-04-25 20:40 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Rennie CLA 2010-10-14 14:29:48 EDT
code from HEAD

While smoke testing the new Run to line support for JSDT, I found that changing the state of the "Skip breakpoints during a run to line" (on the Run/Debug pref page) has no effect on the JSDT run to line operation - breakpoints are still hit.

Consider the example:


function Func(fval){
    var value = fval;
    this.__defineGetter__("value", function(){
        return value; //BP HERE
    });
    
    this.__defineSetter__("value", function(val){
        value = val; //BP HERE
    });
}

var myfunc = new Func("foo"); //BP HERE
myfunc.value = "foo2";
var myvalue = myfunc.value;

function F2() {
	this.name = "";
}

var f2 = new F2();
f2.name = "no";
var f2a = f2.name;

Steps:

1. place breakpoints where indicated
2. debug in Rhino
3. place the cursor on the var myvalue = myfunc.value; line somewhere after execution suspend
4. run to line (Ctrl+R)

Happens:

if with the global setting turned on to ignore breakpoints during a run to line both breakpoints will be hit

Expected:

execution would continue - without breaking - until the var myvalue = myfunc.value; line.