Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: GDB's command qualifier character is `/'
Date: Mon, 20 Oct 2003 21:54:00 -0000	[thread overview]
Message-ID: <vt2y8vfwp60.fsf@zenia.home> (raw)
In-Reply-To: <3F92C0D2.6050807@gnu.org>


Andrew Cagney <cagney@gnu.org> writes:
> GDB's CLI, long ago established `/' as its command qualifier character vis:
> 
> 	x/i
> 	display/i
> 	print/x
> 
> GDB's user base is very familar with this syntax(1) so adding new
> qualfiers using this syntax would provide a consistent user experience
> (if there is x/i, how come there isn't "info break/l"?).

I think / is only for format specifiers, not a general-purpose command
qualifier thing.

It seems to me that GDB has tended to use words for command
qualifiers, like:

  break foo if x == 10
  break foo thread 4
  `append [binary] memory FILENAME START_ADDR END_ADDR'
  `append [binary] value FILENAME EXPR'

We do have some existing examples of Unix-like command options:

  `symbol-file FILENAME [ -readnow ] [ -mapped ]'
  `file FILENAME [ -readnow ] [ -mapped ]'

  `add-symbol-file FILENAME ADDRESS'
  `add-symbol-file FILENAME ADDRESS [ -readnow ] [ -mapped ]'
  `add-symbol-file FILENAME -sSECTION ADDRESS ...'

I'd love to see discussion about how to pull these things together a
bit more, but I think it's difficult to argue that there is a
consistent rule in place already.


      parent reply	other threads:[~2003-10-20 21:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-19 16:50 Andrew Cagney
2003-10-20  0:32 ` Daniel Jacobowitz
2003-10-21 19:29   ` Andrew Cagney
2003-10-22  9:56     ` Andreas Schwab
2003-10-22 14:38       ` Andrew Cagney
2003-10-20 21:54 ` Jim Blandy [this message]

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=vt2y8vfwp60.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=cagney@gnu.org \
    --cc=gdb@sources.redhat.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