public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Schimpe, Christina" <christina.schimpe@intel.com>
To: Pedro Alves <pedro@palves.net>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "aburgess@redhat.com" <aburgess@redhat.com>,
	"eliz@gnu.org" <eliz@gnu.org>, "tom@tromey.com" <tom@tromey.com>
Subject: RE: [PATCH v3 1/3] gdb: Make global feature array a per-remote target array
Date: Tue, 18 Oct 2022 10:26:02 +0000	[thread overview]
Message-ID: <CY4PR11MB2005F4713B593785805192FAF9289@CY4PR11MB2005.namprd11.prod.outlook.com> (raw)
In-Reply-To: <7f3a8e9c-0c75-e8ac-cf01-14b12e5eb96e@palves.net>

Hi Pedro,

Thank you for the review.
The points you mention make sense to me. I added some remarks further down below.
 
> These shouldn't actually be translated, as GDB only accepts these in English.
> Like, in
> 
>   (gdb) set foo off
> 
> "off" is always "off".

Ah, ok. Thanks!

> > +      default:
> > +	return _("internal-error");
> 
> I'd just remove this one.

But we need some sort of default case, right?
I'd replace it with an assert as it's done in other locations, 
e.g. sth. like  gdb_assert_not_reached ("invalid var_auto_boolean");

> So this structure is now a bit odd.  It holds both packet description stuff, like
> the name/title, which is shared between all the remote connections; and
> configuration stuff, which is per-connection.  I think we should split this in
> two structs / arrays, so we only have one copy of the description stuff.
>

That makes sense to me but will cause quite some changes of the current patch.
I will go ahead with two structs and two arrays then.

> In fact, aren't show_cmd/set_cmd above essentially unused after this patch?
> I can only see places writing to those fields, I see nowhere actually reading
> from those fields.  I think you can just drop them entirely.

I agree.


> Missing space before parens in those two set_context calls.

Yes.

> > +
> > +  if (packet_idx >= 0 && packet_idx  < PACKET_MAX)
> 
> Spurious double space in "packet_idx  <".

Yes, thank you.

I will post a v4 of this series soon.

Best Regards,

Christina
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva  
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

  reply	other threads:[~2022-10-18 10:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 15:37 [PATCH v3 0/3] Apply fixme notes for multi-target support Christina Schimpe
2022-09-09 15:37 ` [PATCH v3 1/3] gdb: Make global feature array a per-remote target array Christina Schimpe
2022-10-04 13:48   ` Pedro Alves
2022-10-18 10:26     ` Schimpe, Christina [this message]
2022-09-09 15:37 ` [PATCH v3 2/3] gdb: Add per-remote target variables for memory read and write config Christina Schimpe
2022-09-09 15:57   ` Eli Zaretskii
2022-09-09 15:37 ` [PATCH v3 3/3] gdb: Remove workaround for the vCont packet Christina Schimpe
2022-12-20 20:29   ` Tom Tromey
2022-12-21  7:42     ` Schimpe, Christina
2022-10-04 12:40 ` [PING][PATCH v3 0/3] Apply fixme notes for multi-target support Schimpe, Christina
2022-10-04 12:40   ` Schimpe, Christina

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=CY4PR11MB2005F4713B593785805192FAF9289@CY4PR11MB2005.namprd11.prod.outlook.com \
    --to=christina.schimpe@intel.com \
    --cc=aburgess@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    --cc=tom@tromey.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).