From cb51b708fd7e0ba427f07b3209d0df1d9a0e3f94 Mon Sep 17 00:00:00 2001 From: Markus Metzger Date: Mon, 21 Dec 2020 08:14:55 +0100 Subject: 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 --- gdb/testsuite/ChangeLog | 4 ++++ gdb/testsuite/lib/gdb.exp | 3 +++ 2 files changed, 7 insertions(+) diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index f2c142e..c64ad97 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,7 @@ +2021-02-26 Markus Metzger + + * lib/gdb.exp (use_gdb_stub): Extend comment. + 2021-02-25 Jan Matyas PR gdb/26819 diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp index 60f84d2..1420512 100644 --- 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 -- cgit v1.1