Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Metzger, Markus T via Gdb-patches" <gdb-patches@sourceware.org>
To: Simon Marchi <simon.marchi@polymtl.ca>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 3/4] testsuite, gdb.btrace: skip multi-inferior.exp on gdbserver targets
Date: Mon, 21 Dec 2020 07:27:05 +0000	[thread overview]
Message-ID: <DM5PR11MB1690574F0A30A69DC0226DDDDEC00@DM5PR11MB1690.namprd11.prod.outlook.com> (raw)
In-Reply-To: <285009da-86dc-2075-f7c8-61378948083b@polymtl.ca>

Hello Simon,

Thanks for your review.

> > --- a/gdb/testsuite/gdb.btrace/multi-inferior.exp
> > +++ b/gdb/testsuite/gdb.btrace/multi-inferior.exp
> > @@ -27,6 +27,13 @@ if { [skip_btrace_tests] } {
> >      return -1
> >  }
> >
> > +# This test creates multiple inferiors.  This won't work with all
> > +# gdbserver board files.
> 
> The comment sounds a bit confusing.  It may be interpreted as "this test
> doesn't work with any gdbserver board files", but you mean "this test works
> with some gdbserver board files but not all".
> 
> I think just saying "Test test creates multiple inferiors." is enough to
> explain the [use_gdb_stub] check.  Stub configurations can't spawn inferiors.

I removed the comment altogether given that it now merely duplicates the code.


> Although I think it wouldn't hurt to improve the documentation of the
> use_gdb_stub procedure to explain what it means, as it's a pretty opaque
> concept if you don't already know it.

How about this [1]?  I'll send a separate patch for it.

Regards,
Markus.

[1]
---

diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index e812237d67a..21c822f26a6 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -3589,6 +3589,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
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

  reply	other threads:[~2020-12-21  7:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 15:12 [PATCH] gdb, record: rephrase the 'not recording' error message Markus Metzger via Gdb-patches
2020-12-17 15:12 ` [PATCH 1/4] testsuite, gdb.btrace: make test names unique Markus Metzger via Gdb-patches
2020-12-18 19:34   ` Simon Marchi via Gdb-patches
2020-12-21  7:26     ` Metzger, Markus T via Gdb-patches
2020-12-17 15:12 ` [PATCH 2/4] testsuite, gdb.python: make py-record-*.exp " Markus Metzger via Gdb-patches
2020-12-18 19:35   ` Simon Marchi via Gdb-patches
2020-12-17 15:12 ` [PATCH 3/4] testsuite, gdb.btrace: skip multi-inferior.exp on gdbserver targets Markus Metzger via Gdb-patches
2020-12-18 19:49   ` Simon Marchi via Gdb-patches
2020-12-21  7:27     ` Metzger, Markus T via Gdb-patches [this message]
2020-12-21 13:50       ` Simon Marchi via Gdb-patches
2020-12-17 15:12 ` [PATCH 4/4] testsuite, gdb.btrace: fix 32-bit PIE false positives Markus Metzger via Gdb-patches
2020-12-18 20:01   ` Simon Marchi via Gdb-patches
2020-12-21  7:27     ` Metzger, Markus T via Gdb-patches
2020-12-18 19:18 ` [PATCH] gdb, record: rephrase the 'not recording' error message Simon Marchi via Gdb-patches

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM5PR11MB1690574F0A30A69DC0226DDDDEC00@DM5PR11MB1690.namprd11.prod.outlook.com \
    --to=gdb-patches@sourceware.org \
    --cc=markus.t.metzger@intel.com \
    --cc=simon.marchi@polymtl.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox