From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/9] gdb/python: new Progspace.executable_filename attribute
Date: Sat, 16 Sep 2023 13:55:29 +0300 [thread overview]
Message-ID: <83bke2idzy.fsf@gnu.org> (raw)
In-Reply-To: <4c77a079079814ae5d476b5fc61b2e25539bd37f.1694858967.git.aburgess@redhat.com> (message from Andrew Burgess via Gdb-patches on Sat, 16 Sep 2023 11:18:04 +0100)
> Date: Sat, 16 Sep 2023 11:18:04 +0100
> From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
>
> Add a new Progspace.executable_filename attribute that contains the
> path to the executable for this program space, or None if no
> executable is set.
>
> The path within this attribute will be set by the "exec-file" and/or
> "file" commands.
>
> Accessing this attribute for an invalid program space will raise an
> exception.
>
> This new attribute is similar too, but not the same as the existing
> gdb.Progspace.filename attribute. If I could change the past, I'd
> change the 'filename' attribute to 'symbol_filename', which is what it
> actually represents. The old attribute will be set by the
> 'symbol-file' command, while the new attribute is set by the
> 'exec-file' command. Obviously the 'file' command sets both of these
> attributes.
> ---
> gdb/NEWS | 6 ++
> gdb/doc/python.texi | 15 ++++
> gdb/python/py-progspace.c | 21 +++++
> gdb/testsuite/gdb.python/py-exec-file.c | 22 +++++
> gdb/testsuite/gdb.python/py-exec-file.exp | 100 ++++++++++++++++++++++
> 5 files changed, 164 insertions(+)
> create mode 100644 gdb/testsuite/gdb.python/py-exec-file.c
> create mode 100644 gdb/testsuite/gdb.python/py-exec-file.exp
Thanks.
> diff --git a/gdb/NEWS b/gdb/NEWS
> index f2f5dabb287..93bc9c6a2c0 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -291,6 +291,12 @@ info main
> Progspace.filename is not None), otherwise, this attribute is
> itself None.
>
> + ** New attribute Progspace.executable_filename. This attribute
> + holds a string containing a path set by the "exec-file" or "file"
> + commands, or None if no executable file is set. This isn't the
> + exact string passed by the user to these commands; the path will
> + have been partially resolved to an absolute path.
GNU Coding Standards frown on using "path" for anything but PATH-style
directory lists. So please use "file name" here.
> diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
> index 03299cc3cf7..206cf6b4e18 100644
> --- a/gdb/doc/python.texi
> +++ b/gdb/doc/python.texi
> @@ -5059,6 +5059,21 @@
> access this attribute will raise a @code{RuntimeError} exception.
> @end defvar
>
> +@defvar Progspace.executable_filename
> +The file name, as a string, of the executable file in use by this
> +program space. The executable file is the file that @value{GDBN} will
> +invoke in order to start an inferior when using a native target. The
> +file name within this attribute is updated by the @kbd{exec-file} and
> +@kbd{file} commands.
> +
> +If no executable is currently set within this @code{Progspace} then
> +this attribute contains @code{None}.
> +
> +If the @code{Progspace} is invalid, i.e.@:, when
> +@code{Progspace.is_valid()} returns @code{False}, then attempting to
> +access this attribute will raise a @code{RuntimeError} exception.
> +@end defvar
This part is OK.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2023-09-16 10:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 10:18 [PATCH 0/9] Add executable_changed event to Python API Andrew Burgess
2023-09-16 10:18 ` [PATCH 1/9] gdb/doc: extend the description for Progspace.filename Andrew Burgess
2023-09-16 10:53 ` Eli Zaretskii
2023-09-16 10:18 ` [PATCH 2/9] gdb/python: new Progspace.symbol_file attribute Andrew Burgess
2023-09-16 10:56 ` Eli Zaretskii
2023-09-16 10:18 ` [PATCH 3/9] gdb/python: new Progspace.executable_filename attribute Andrew Burgess
2023-09-16 10:55 ` Eli Zaretskii [this message]
2023-09-16 10:18 ` [PATCH 4/9] gdb: remove one user of the executable changed observer Andrew Burgess
2023-09-16 10:18 ` [PATCH 5/9] gdb: remove final user of the executable_changed observer Andrew Burgess
2023-09-16 10:18 ` [PATCH 6/9] gdb: remove unnecessary notification of " Andrew Burgess
2023-09-16 10:18 ` [PATCH 7/9] gdb: pass more arguments to the " Andrew Burgess
2023-09-16 10:18 ` [PATCH 8/9] gdb/python: make the executable_changed event available from Python Andrew Burgess
2023-09-16 11:03 ` Eli Zaretskii
2023-09-28 14:35 ` Andrew Burgess
2023-09-16 10:18 ` [PATCH 9/9] gdb: use reopen_exec_file from reread_symbols Andrew Burgess
2023-09-19 14:08 ` Tom Tromey
2023-09-28 15:23 ` Andrew Burgess
2023-09-28 18:15 ` Tom Tromey
2023-09-29 10:17 ` Andrew Burgess
2023-09-29 15:18 ` Eli Zaretskii
2023-10-02 14:16 ` Tom Tromey
2023-09-29 14:42 ` Eli Zaretskii
2023-10-02 14:02 ` Tom Tromey
2023-10-02 16:19 ` Eli Zaretskii
2023-09-19 14:09 ` [PATCH 0/9] Add executable_changed event to Python API 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=83bke2idzy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).