From 376f1cb9c1c4e7bf05328e56e33b134f0dbd62af Mon Sep 17 00:00:00 2001 From: Marc Khouzam Date: Fri, 20 Aug 2010 18:01:44 +0000 Subject: [PATCH] Bug 323276: We were using the wrong context when clearing the cache for the "Force thread list update" feature, with GDB 7.0 or later --- .../org/eclipse/cdt/dsf/gdb/service/GDBProcesses_7_0.java | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) 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 597123eb7dc..d9c9fbd0497 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 @@ -978,7 +978,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) {} }