From: Joel Brobecker <brobecker@adacore.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [patch] Add solib_address and decode_line Python functionality
Date: Tue, 27 Jul 2010 16:26:00 -0000 [thread overview]
Message-ID: <20100727162545.GF13267@adacore.com> (raw)
In-Reply-To: <4C44728D.4040408@redhat.com>
Just my 2 cents on the API and doc...
> solib_address -- lookup an address and if it resides in an solib
> reports that libs name, or None.
IMO, the name that was chosen for this function implies the opposite
of what it does (it implies that it returns the solib (base?) address).
I would personally prefer solib_name or solib_name_from_address.
> +for Python commands (@pxref{Commands In Python}). The expected
> +format of @var{expression} is:
> +
> +@table @code
> +@item FILE:LINENUM
> +A location indicated at that line in that file.
> +@item FUNCTION
> +A location at the beginning of that function.
> +@item FILE:FUNCTION
> +A location to distinguish among like-named static functions.
> +@item ADDRESS
> +A location containing that address.
> +@item VARIABLE
> +A location containing that variable.
> +@end table
> +@end defun
ISTM that we would be better off not duplicating the various forms
a linespec can take. How about using a cross reference?
--
Joel
next prev parent reply other threads:[~2010-07-27 16:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 15:43 Phil Muldoon
2010-07-27 16:26 ` Joel Brobecker [this message]
2010-07-28 11:35 ` Phil Muldoon
2010-07-28 17:39 ` Joel Brobecker
2010-07-28 17:48 ` Eli Zaretskii
2010-07-29 20:39 ` Tom Tromey
2010-08-06 13:55 ` Phil Muldoon
2010-08-06 15:36 ` Eli Zaretskii
2010-08-06 22:39 ` Tom Tromey
2010-08-10 11:17 ` Phil Muldoon
2010-08-10 17:07 ` Eli Zaretskii
2010-08-10 18:24 ` Tom Tromey
2010-08-11 13:16 ` Phil Muldoon
2010-08-13 14:07 ` Ken Werner
2010-08-13 14:14 ` Phil Muldoon
2010-08-13 15:48 ` Tom Tromey
2010-08-13 16:22 ` Ken Werner
2010-08-18 23:55 ` Pedro Alves
2010-08-19 16:32 ` Tom Tromey
2010-08-19 17:04 ` Pedro Alves
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=20100727162545.GF13267@adacore.com \
--to=brobecker@adacore.com \
--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