From 1dab23830773a7d008b7d886b31c3466e9f5027c Mon Sep 17 00:00:00 2001
From: hjk <qtc-committer@nokia.com>
Date: Wed, 8 Sep 2010 11:54:33 +0200
Subject: [PATCH] debugger: add some comment on 'set target-async' weirdness
---
.../debugger/gdb/remotegdbserveradapter.cpp | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/src/plugins/debugger/gdb/remotegdbserveradapter.cpp b/src/plugins/debugger/gdb/remotegdbserveradapter.cpp
index f3749f402ab..86fa9edfc4b 100644
--- a/src/plugins/debugger/gdb/remotegdbserveradapter.cpp
+++ b/src/plugins/debugger/gdb/remotegdbserveradapter.cpp
@@ -184,6 +184,20 @@ void RemoteGdbServerAdapter::setupInferior()
if (!args.isEmpty())
m_engine->postCommand("-exec-arguments " + args.toLocal8Bit());
+ // This has to be issued before 'target remote'. On pre-7.0 the
+ // command is not present and will result in ' No symbol table is
+ // loaded. Use the "file" command.' as gdb tries to set the
+ // value of a variable with name 'target-async'.
+ //
+ // Testing with -list-target-features which was introduced at
+ // the same time would not work either, as this need an existing
+ // target.
+ //
+ // Using it even without a target and having it fail might still
+ // be better as:
+ // Some external comment: '[but] "set target-async on" with a native
+ // windows gdb will work, but then fail when you actually do
+ // "run"/"attach", I think..
m_engine->postCommand("set target-async on", CB(handleSetTargetAsync));
if (fileName.isEmpty()) {
--
GitLab