public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Schimpe, Christina" <christina.schimpe@intel.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 1/3] gdb: Make global feature array a per-remote target array
Date: Thu, 20 Jan 2022 17:24:01 +0000	[thread overview]
Message-ID: <BYAPR11MB3590410BE6D9398ECAFCEE2BF95A9@BYAPR11MB3590.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220118113032.GD622389@redhat.com>

Thanks for the feedback.

> Could you update your examples to not use implicit values here
> please.  This just makes reading these that little bit harder for no
> reason.

Yes, you are right. I will update this.
 
> However, I do think there are some things we could do to make it clear
> what's going on, I think that the string printed for 'show remote
> PACKET-NAME' should be updated to reflect what it's showing, as in:
> 
>   (gdb) show remote kill-packet
>   Support for the `vKill' packet on the current remote target, is "auto"
> (currently unknown).
> 
> OR
> 
>   (gdb) show remote kill-packet
>   Support for the `vKill' packet on newly created remote targets, is "auto".
> 
> Notice, I dropped the 'currently unknown' as that makes no sense when
> talking about the future targets.
> 
> I also think we should have the set command print something to tell
> the user what changed, so they can know if they messed up, maybe:
> 
>  (gdb) set remote kill-packet off
>  Use of the 'vKill' packet for the current, and future remote targets, set to
> "off".
> 
> OR
> 
>  (gdb) set remote kill-packet off
>  Use of the 'vKill' packet for future remote targets, set to "off".

Yes, that makes sense to me. I will adapt the set/show command prints,
as well as all the tests using the set/show commands. 

> 
> This change absolutely needs a NEWS entry and also a documentation
> update.
> 
> With one exception the rest of my feedback is basically: there should
> be more comments added.  I know that sucks, especially when working in
> older files like remote.c, where the initial code is poorly commented
> anyway, but for me good comments do help understand what the intention
> of a field or struct is, so I think, when we change stuff, we should
> take the opportunity to document what's going on.  So...

I also agree with the rest of your comments and will send a V2 for this soon.

Thanks,
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-01-20 17:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 15:21 [PATCH 0/3] Apply fixme notes for multi-target support Christina Schimpe
2022-01-13 15:21 ` [PATCH 1/3] gdb: Make global feature array a per-remote target array Christina Schimpe
2022-01-14 19:30   ` Tom Tromey
2022-01-20 16:32     ` Schimpe, Christina
2022-01-18 11:30   ` Andrew Burgess
2022-01-20 17:24     ` Schimpe, Christina [this message]
2022-01-13 15:21 ` [PATCH 2/3] gdb: Add per-remote target variables for memory read and write config Christina Schimpe
2022-01-14 19:33   ` Tom Tromey
2022-01-18 11:39   ` Andrew Burgess
2022-01-24 15:06     ` Schimpe, Christina
2022-02-04 18:03       ` Andrew Burgess
2022-01-13 15:21 ` [PATCH 3/3] gdb: Remove workaround for the vCont packet Christina Schimpe
2022-01-14 19:42   ` Tom Tromey
2022-01-28 13:28     ` 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=BYAPR11MB3590410BE6D9398ECAFCEE2BF95A9@BYAPR11MB3590.namprd11.prod.outlook.com \
    --to=christina.schimpe@intel.com \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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).