From 5614e9339a722b7b69793d6e5a7278c6c0b6e404 Mon Sep 17 00:00:00 2001 From: Marc Khouzam Date: Thu, 20 Nov 2008 14:19:33 +0000 Subject: [PATCH] [255968] The connect action was enabled after the inferior terminated on its own. It should only be enabled in the case of an attach session. --- .../gdb/internal/provisional/service/GDBProcesses.java | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/plugins/org.eclipse.dd.gdb/src/org/eclipse/dd/gdb/internal/provisional/service/GDBProcesses.java b/plugins/org.eclipse.dd.gdb/src/org/eclipse/dd/gdb/internal/provisional/service/GDBProcesses.java index 7bfc24db448..0378e123d28 100644 --- a/plugins/org.eclipse.dd.gdb/src/org/eclipse/dd/gdb/internal/provisional/service/GDBProcesses.java +++ b/plugins/org.eclipse.dd.gdb/src/org/eclipse/dd/gdb/internal/provisional/service/GDBProcesses.java @@ -154,7 +154,15 @@ public class GDBProcesses extends MIProcesses { @Override public void isDebuggerAttachSupported(IDMContext dmc, DataRequestMonitor rm) { - rm.setData(!fGdb.isConnected()); + MIInferiorProcess inferiorProcess = fGdb.getInferiorProcess(); + if (!fGdb.isConnected() && + inferiorProcess != null && + inferiorProcess.getState() != MIInferiorProcess.State.TERMINATED) { + + rm.setData(true); + } else { + rm.setData(false); + } rm.done(); }