| Summary: | Run to line hits breakpoints even with the platform setting to skip them turned on | ||
|---|---|---|---|
| Product: | [WebTools] JSDT | Reporter: | Michael Rennie <Michael_Rennie> |
| Component: | Debug | Assignee: | Project Inbox <jsdt.debug-inbox> |
| Status: | NEW --- | QA Contact: | Simon Kaegi <simon_kaegi> |
| Severity: | normal | ||
| Priority: | P3 | CC: | jzhang, thatnitind |
| Version: | 3.3 | ||
| Target Milestone: | Future | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
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.