From: Eli Zaretskii <eliz@gnu.org>
To: Siva Chandra <sivachandra@google.com>
Cc: gdb-patches@sourceware.org, dje@google.com, tromey@redhat.com
Subject: Re: [RFC - Python Scripting] New method gdb.Architecture.disassemble
Date: Tue, 19 Feb 2013 16:38:00 -0000 [thread overview]
Message-ID: <83k3q4p8bu.fsf@gnu.org> (raw)
In-Reply-To: <CAGyQ6gyAwQpBJ41bOtvQOGKM+OM+7eKQ1TVdTC7-G3O1RG0Geg@mail.gmail.com>
> Date: Mon, 18 Feb 2013 21:36:00 -0800
> From: Siva Chandra <sivachandra@google.com>
> Cc: gdb-patches@sourceware.org, dje@google.com, tromey@redhat.com
>
> On Sat, Feb 16, 2013 at 12:47 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> >> +@defun Architecture.disassemble (@var{start_pc} @r{[}, @var{end_pc} @r{[}, @var{count}@r{]]})
> >> +Return a list of at most @var{count} disassembled instructions
> >> +whose start address falls in the closed memory address interval from
> >> +@var{start_pc} to @var{end_pc}. If @var{end_pc} is not specified, but
> >> +@var{count} is specified, then @var{count} number of instructions
> >> +starting from the address @var{start_pc} are returned. If @var{count}
> >> +is not specified but @var{end_pc} is specified, then all instructions
> >> +whose start address falls in the closed memory address interval from
> >> +@var{start_pc} to @var{end_pc} are returned. If neither @var{end_pc}
> >> +nor @var{count} are specified, then a single instruction at
> >> +@var{start_pc} is returned.
> >
> > The description of the optional arguments makes sense, but the @defun
> > line is in contradiction with the description, because it says that
> > one can specify all 3 arguments. IOW, there should be a '|' somewhere
> > to signal that either end_pc or count, but not both, could be used.
> >
>
> One can specify all three arguments. Does the description anywhere
> indicate otherwise?
The text does not describe that possibility at all, so I assumed that
it cannot happen.
next prev parent reply other threads:[~2013-02-19 16:38 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 14:09 Siva Chandra
2013-02-05 23:28 ` Doug Evans
2013-02-06 1:53 ` Siva Chandra
2013-02-06 20:00 ` Tom Tromey
2013-02-08 18:05 ` Doug Evans
2013-02-09 17:55 ` Matt Rice
2013-02-12 14:56 ` Siva Chandra
2013-02-12 21:18 ` Tom Tromey
2013-02-13 14:37 ` Siva Chandra
2013-02-13 17:52 ` Eli Zaretskii
2013-02-13 18:03 ` Tom Tromey
2013-02-13 19:50 ` Siva Chandra
2013-02-13 20:42 ` Doug Evans
2013-02-14 22:46 ` Siva Chandra
2013-02-15 6:43 ` Doug Evans
2013-02-15 17:32 ` Doug Evans
2013-02-15 17:40 ` Siva Chandra
2013-02-15 17:41 ` Siva Chandra
2013-02-15 18:57 ` Doug Evans
2013-02-15 20:36 ` Siva Chandra
2013-02-15 21:01 ` Siva Chandra
2013-02-16 5:30 ` Doug Evans
2013-02-16 8:47 ` Eli Zaretskii
2013-02-19 5:36 ` Siva Chandra
2013-02-19 15:51 ` Paul_Koning
2013-02-19 16:35 ` Eli Zaretskii
2013-02-19 16:38 ` Eli Zaretskii [this message]
2013-02-20 12:34 ` Siva Chandra
2013-02-20 18:44 ` Eli Zaretskii
2013-02-21 1:49 ` Siva Chandra
2013-02-06 19:58 ` Tom Tromey
2013-02-06 20:31 ` Phil Muldoon
2013-02-06 22:31 ` Matt Rice
2013-02-06 23:19 ` Siva Chandra
2013-02-07 1:11 ` Siva Chandra
2013-02-07 23:03 ` Matt Rice
[not found] ` <20130206235707.GA2353@klara.mpi.htwm.de>
2013-02-07 1:18 ` Siva Chandra
2013-02-07 14:14 ` Siva Chandra
2013-02-07 16:42 ` Tom Tromey
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=83k3q4p8bu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=sivachandra@google.com \
--cc=tromey@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