testsuite: note on use_gdb_stub usage

Add a note to the comment on use_gdb_stub explaining the use of this check
for skipping tests that spawn new inferiors as discussed here:

    https://sourceware.org/pipermail/gdb-patches/2020-December/174186.html

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index f2c142e6b941524df775f2468809a9b10ffb4d6d..c64ad978e4ab7538297629761f41fcb431b32a2f 100644 (file)
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,7 @@
+2021-02-26  Markus Metzger  <markus.t.metzger@intel.com>
+
+       * lib/gdb.exp (use_gdb_stub): Extend comment.
+
 2021-02-25  Jan Matyas  <jmatyas@codasip.com>
 
        PR gdb/26819

diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 60f84d22aadea2756d5d8f5eff662cc828d4b760..142051296cbf9e9349d8bf1106d8f058fbf3af99 100644 (file)
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -3646,6 +3646,9 @@ proc gdb_is_target_native { } {
 # This is the preferred way of checking use_gdb_stub, since it allows to check
 # the value before the gdb has been spawned and it will return the correct value
 # even when it was overriden by the test.
+#
+# Note that stub targets are not able to spawn new inferiors.  Use this
+# check for skipping respective tests.
 
 proc use_gdb_stub {} {
   global use_gdb_stub