Bug 310274: Need to set the fInterruptFailedJob to null in the executor to avoid multi-threaded issues

1 files changed, 1 insertions, 1 deletions

diff --git a/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/gdb/service/GDBBackend.java b/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/gdb/service/GDBBackend.java
index 8fd86f9b9ab..8b93ff08882 100644
--- a/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/gdb/service/GDBBackend.java
+++ b/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/gdb/service/GDBBackend.java
@@ -695,10 +695,10 @@ public class GDBBackend extends AbstractDsfService implements IGDBBackend {
 
         @Override
         protected IStatus run(IProgressMonitor monitor) {
-        	fInterruptFailedJob = null;
         	getExecutor().submit(
                     new DsfRunnable() {
                         public void run() {
+                        	fInterruptFailedJob = null;
                         	fRequestMonitor.setStatus(new Status(IStatus.ERROR, GdbPlugin.PLUGIN_ID, IDsfStatusConstants.REQUEST_FAILED, "Interrupt failed.", null)); //$NON-NLS-1$
                         	fRequestMonitor.done();
                         }