Description Michael Rennie 2011-01-27 15:54:07 EST

I20110126-1800

Steps:
1. Create a build file with a long running task (or use the example buildfile below)
2. Place a breakpoint at the start of the build file and debug it
3. once it suspends, try resuming in a number of ways:
  a. F8 with the stackframe selected
  b. F8 with the debug target selected
  c. F8 with the thread selected
  d. F6 till it resumes
4. notice that:
  a. the debug target still says it is suspended
  b. nothing is updated and the stackframe is still present
  c. the stackframe goes away but the target still thinks it is suspended
  d. the thread thinks it is resumed, the target still thinks it is suspended and the stackframe does not go away

In all cases I would expect the stackframe to go away and the target and thread to be shown as resumed. Double-clicking the debug target causes the view to refresh and the correct state to be shown, so our model is in the correct state, but the view is not being updated correctly.

Perhaps we are not firing the correct DebugEvents anymore.

Example buildfile:

<?xml version="1.0" encoding="UTF-8"?>
<project name="project" default="default">
    <target name="default" description="description">
    	<property name="xml" value="/home/mrennie/use/xml/"/> // BP HERE
        <apitooling.apiuse
        	report="${xml}"
        	scopepattern=".*"
        	considerapi="true"
        	location="/eclipse/eclipse/"
        	apipatterns=".*"
        	internalpatterns=".*"
        	debug="true"
        />
    </target>
</project>