Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 327270 - Hitting a breakpoint during a step causes debug buttons to disable
Summary: Hitting a breakpoint during a step causes debug buttons to disable
Status: RESOLVED FIXED
Alias: None
Product: JSDT
Classification: WebTools
Component: Debug (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.2.3   Edit
Assignee: Michael Rennie CLA
QA Contact: Simon Kaegi CLA
URL:
Whiteboard:
Keywords:
Depends on: 326809
Blocks: 327278
  Show dependency tree
 
Reported: 2010-10-07 14:54 EDT by Simon Kaegi CLA
Modified: 2010-10-19 16:23 EDT (History)
2 users (show)

See Also:
thatnitind: review+


Attachments
fix (1.12 KB, patch)
2010-10-07 15:23 EDT, Michael Rennie CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Kaegi CLA 2010-10-07 14:54:57 EDT
+++ This bug was initially created as a clone of Bug #326809 +++

code from HEAD

debug the following snippet:

function Func(fval){
    this.__defineSetter__("value", function(val){
        value = val;  //bp here
    });
}

var myfunc = new Func("foo"); //bp here
myfunc.value = "foo2";

and step over until you hit the breakpoint in __defineSetter__. Notice that all of the debugging buttons (step over / into / out) are all disabled.

Taking a quick look revealed that we still think we are stepping in this case, so when the commands poll for enablement (canStep) we say no.

We should be handling the case of hitting a breakpoint while stepping - we already handle resuming while stepping.
Comment 1 Michael Rennie CLA 2010-10-07 15:23:51 EDT
Created attachment 180448 [details]
fix
Comment 2 Michael Rennie CLA 2010-10-19 16:22:24 EDT
applied patch to 3.2.3, please verify Nitin