This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RFC: "set" command with 2 arguments instead of one?
- From: Joel Brobecker <brobecker at adacore dot com>
- To: gdb-patches at sourceware dot org
- Date: Sun, 23 Nov 2014 08:24:17 +0400
- Subject: RFC: "set" command with 2 arguments instead of one?
- Authentication-results: sourceware.org; auth=none
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