Bug 323276: We were using the wrong context the clear the cache for the "Force thread list update" feature, with GDB 7.0 or later

1 files changed, 4 insertions, 1 deletions

diff --git a/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/gdb/service/GDBProcesses_7_0.java b/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/gdb/service/GDBProcesses_7_0.java
index 8af45e55cc7..42196ad20e2 100644
--- a/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/gdb/service/GDBProcesses_7_0.java
+++ b/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/gdb/service/GDBProcesses_7_0.java
@@ -949,7 +949,10 @@ public class GDBProcesses_7_0 extends AbstractDsfService
 		// 280631
    		try {
 			if (fBackend.getUpdateThreadListOnSuspend()) {
-				fThreadCommandCache.reset(e.getDMContext());
+				// We need to clear the cache for the context that we use to fill the cache,
+				// and it is the controDMC in this case.
+				ICommandControlDMContext controlDmc = DMContexts.getAncestorOfType(e.getDMContext(), ICommandControlDMContext.class);
+				fThreadCommandCache.reset(controlDmc);
 			}
 		} catch (CoreException exc) {}
     }