Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch][python] Add symbol, symbol table and frame block support   to GDB API
Date: Fri, 05 Feb 2010 11:05:00 -0000	[thread overview]
Message-ID: <83r5p0eyer.fsf@gnu.org> (raw)
In-Reply-To: <4B69E2C6.3090509@redhat.com>

> Date: Wed, 03 Feb 2010 20:55:34 +0000
> From: Phil Muldoon <pmuldoon@redhat.com>
> CC: gdb-patches@sourceware.org
> 
> This is a multi-part message in MIME format.
> --------------050506000002080100010500
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: 7bit
> 
> On 02/02/2010 08:14 PM, Eli Zaretskii wrote:
> 
> >>>> +All of the name-scope contours of a program are represented as 'block'
> >>>
> >>> What are "contours"?  Is this a widespread enough terminology to be
> >>> understood without defining it first?  If not, I suggest to define it.
> >>
> >>
> >> I really agonized over the whole block description, as there is no (as
> >> far as I know) analogue to the GDB CLI for blocks.  It's revealing an
> >> API that GDB uses to manipulate blocks in a frame.  I could use some
> >> help making this more palatable enough to the consumer of the API,
> >> over trying to teach the user compiler/runtime semantics (which is not
> >> the purpose of the GDB manual).  What do you think?
> > 
> > How about if you tell what you want in the most technical way you
> > think about these issues, disregarding the fact that it's for GDB
> > users, and I will then rephrase it to be palatable to mere mortals?
> 
> 
> I've attached an updated patch.  What do you think?

It's good, thanks.  I have only a couple of comments:

> +@defivar Symbol is_argument
> +Is @code{True} if the symbol is an argument of a function.

I'd prefer to drop the "Is" part altogether, here and elsewhere.

> +@findex SYMBOL_LOC_ARG
> +@findex gdb.SYMBOL_LOC_ARG
> +@item SYMBOL_LOC_ARG
> +Value is an argument.

The comment in the source says:

  /* It's an argument; the value is at SYMBOL_VALUE offset in arglist.  */

Should we expand the above description by adding some text from the
comment?

> +@findex SYMBOL_LOC_REF_ARG
> +@findex gdb.SYMBOL_LOC_REF_ARG
> +@item SYMBOL_LOC_REF_ARG
> +Value address is an offset in arglist.

The comment in the code seems to be a continuation of the previous
comment (shown above).  Again, perhaps we should say more.  Can you or
someone else explain what these constants mean, i.e. say a bit more
than the comment says?


  parent reply	other threads:[~2010-02-05 11:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01 13:42 Phil Muldoon
2010-02-01 20:54 ` Eli Zaretskii
2010-02-02 10:24   ` Phil Muldoon
2010-02-02 20:14     ` Eli Zaretskii
2010-02-03 20:55       ` Phil Muldoon
2010-02-05 10:53         ` Phil Muldoon
2010-02-05 18:06           ` Eli Zaretskii
2010-02-05 11:05         ` Eli Zaretskii [this message]
2010-02-04 23:25 ` Tom Tromey
2010-02-15 15:15   ` Phil Muldoon
2010-02-15 18:45     ` Eli Zaretskii
2010-02-15 23:39       ` Phil Muldoon
2010-02-16  4:12         ` Eli Zaretskii
2010-02-18  2:50     ` Tom Tromey
2010-02-19 14:15       ` Phil Muldoon
2010-02-19 14:28         ` Eli Zaretskii
2010-02-19 15:13           ` Phil Muldoon
2010-02-23 23:05         ` Tom Tromey
2010-02-24 16:58           ` Phil Muldoon
2010-02-24 17:22             ` Tom Tromey
2010-02-24 21:49               ` Phil Muldoon
2010-02-24 18:43             ` Eli Zaretskii
2010-02-23 23:09         ` 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=83r5p0eyer.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@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