Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: RFC: "set" command with 2 arguments instead of one?
Date: Sun, 23 Nov 2014 04:24:00 -0000	[thread overview]
Message-ID: <20141123042417.GA839@adacore.com> (raw)

Hello everyone,

Please see the following patch submission:
https://www.sourceware.org/ml/gdb-patches/2014-09/msg00869.html

It proposes the introduction of a couple of commands, one to dump
the contents of the of the bounds table, and one to set the bounds
for any given address. Since those commands are MPX-specific,
I would like to have them prefixed somehow. But the beyond the
fact that I'd like to have them prefixed, I was wondering if
set/show commands could be used for that. Eg:

    show mpx bound ADDR
    set mpx bound ADDR LBOUND UBOUND

The reason why I am asking for comments is that the "set" command
above has a syntax which is slightly unusual for "set" commands
in the sense that "set" commands nearly always only have one argument,
whereas it has 3 in this case.

I don't think that's an actual issue, as I don't see why we would
not want that and I do feel that "set mpx bound" sounds pretty
natural.

Any thoughts on the above?

Thank you!
-- 
Joel


             reply	other threads:[~2014-11-23  4:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-23  4:24 Joel Brobecker [this message]
2014-11-23  9:32 ` Andreas Schwab
2014-11-23  9:53   ` Joel Brobecker
2014-11-24  5:39     ` Doug Evans
2014-11-24  7:13       ` Joel Brobecker
2014-11-24 10:38         ` Andreas Schwab
2014-11-24 15:36         ` Doug Evans
2015-04-13 15:32         ` Tedeschi, Walfred
2015-04-14 12:49           ` Joel Brobecker
2015-04-20  5:44             ` Doug Evans
2015-04-20 15:25               ` Joel Brobecker
2015-04-20 15:30               ` Tedeschi, Walfred

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=20141123042417.GA839@adacore.com \
    --to=brobecker@adacore.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