Community
Participate
Working Groups
N20111011-2000. 1. start debugging 2. close the Debug view 3. click the Debug Toolbar buttons ==> nothing happens
I checked on this before committing the latest implementation. When I try this workflow, I can actually continue debugging, just without the Debug view showing me the current context (i.e. the selection in the editor changes, variables view refreshes, etc.). Do you see something different? Also, as soon as the target suspends (after a step, etc.) the Debug view is shown, unless the preference "Activate the debug view when breakpoint is hit" is changed.
(In reply to comment #1) > I checked on this before committing the latest implementation. When I try this > workflow, I can actually continue debugging, just without the Debug view > showing me the current context (i.e. the selection in the editor changes, > variables view refreshes, etc.). Do you see something different? Yes, it does not work using N20111011-2000: 1. start new workspace 2. paste: public static void main(String[] args) { System.out.println(1); System.out.println(2); System.out.println(3); } 3. Debug As > Java Application 4. choose 'yes' to switch perspective 5. close Debug view ==> buttons don't work
Thank you for the steps to reproduce. Looks like a bug we introduced last year with support for pin and clone, but nobody noticed since the affected run control actions were in the menu. I pushed the fix to master, please verify.
Verified in N20111013-2000.
