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: Tue, 02 Feb 2010 20:14:00 -0000	[thread overview]
Message-ID: <83hbpzgztm.fsf@gnu.org> (raw)
In-Reply-To: <4B67FD58.5050504@redhat.com>

> Date: Tue, 02 Feb 2010 10:24:24 +0000
> From: Phil Muldoon <pmuldoon@redhat.com>
> CC: gdb-patches ml <gdb-patches@sourceware.org>
> 
> >> +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?

> >> +@value{GDBN} represents the name of every variable, function and type
> >> +as a symbol (@pxref{Symbols, ,Examining the Symbol Table}).
> > 
> > I think, from the GDB user POV, a name of a variable, function, and
> > type is just a string, not a symbol.
> 
> But in the context of the Python API, they are represented as symbols?  How should I word this?

How about

  @value{GDBN} represents every variable, function and type as a an
  entry in a symbol table.

> >> +@item SYMBOL_LOC_REF_ARG
> >> +Value address is an offset in arglist.
> > 
> > I couldn't understand what this means.
> 
> 
> Yeah, this is a concept expressed in the comments of the code.

Where?  I don't see it in the patch you submitted.

> > Do we need a NEWS entry for this?
> 
> Not sure. From my point of view I am merging code from Archer to FSF
> GDB. I'll happily write one up if you think we need one? What do you
> think?

Something like

  The GDB Python API now has access to symbols, symbol tables, and
  frame's code blocks.

Thanks.


  reply	other threads:[~2010-02-02 20:14 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 [this message]
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
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=83hbpzgztm.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