Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: "Nick Roberts" <nickrob@snap.net.nz>, "Eli Zaretskii" <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [Patch:Doc] Example for -exec-arguments
Date: Fri, 06 Jun 2008 13:24:00 -0000	[thread overview]
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA04291186@ecamlmw720.eamcs.ericsson.se> (raw)
In-Reply-To: <18504.22062.565990.33175@kahikatea.snap.net.nz>

> -exec-arguments is just "set args" really.  The number of 
> such commands that
> could be created are almost limitless.  Note that this one 
> provides no output
> for the MI front end to parse and the CLI command could 
> easily be used.  I
> wonder if they are really needed and whether we should remove 
> them (or at least
> the ones which are unimplemented).

Now that you point this out, I realize we can use "-gdb-set args" right now.
Not only that, but -gdb-show args does works while -exec-show-arguments
does not.

I prefer to use -gdb-set since I can.

>  > > Also, the doc mentions -exec-show-arguments, but the actual
>  > > implementation in GDB is missing.  Should this be 
> written in the doc?
>  > 
>  > Yes, I think so.
> 
> That's what is written in the docs:
> 
>    Example
>    .......
>  
>    Example(s) formatted for readability.  Some of the 
> described commands
>    have not been implemented yet and these are labeled N.A. (not
>    available).

You are right.  I had seen the N.A. and thought that just the example was not
available, not the whole command.

Marc


      reply	other threads:[~2008-06-06 13:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05 18:59 Marc Khouzam
2008-06-05 19:25 ` Eli Zaretskii
2008-06-05 21:10   ` Nick Roberts
2008-06-06 13:24     ` Marc Khouzam [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=6D19CA8D71C89C43A057926FE0D4ADAA04291186@ecamlmw720.eamcs.ericsson.se \
    --to=marc.khouzam@ericsson.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nickrob@snap.net.nz \
    /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