From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] Change how Python architecture and language are handled
Date: Mon, 10 Jan 2022 14:22:16 -0700 [thread overview]
Message-ID: <87zgo3l20n.fsf@tromey.com> (raw)
In-Reply-To: <878rvnmgvk.fsf@tromey.com> (Tom Tromey's message of "Mon, 10 Jan 2022 14:15:59 -0700")
>>> - gdbpy_enter (struct gdbarch *gdbarch, const struct language_defn *language);
>>> + explicit gdbpy_enter (struct gdbarch *gdbarch = nullptr,
>>> + const struct language_defn *language = nullptr);
Andrew> I know the old code was not commented, but it would be awesome if we
Andrew> could take this opportunity to add a description of what the function
Andrew> does, and what the parameters are used for.
Tom> Will do.
Some of it is documented at the 'class' level:
/* Called before entering the Python interpreter to install the
current language and architecture to be used for Python values.
Also set the active extension language for GDB so that SIGINT's
are directed our way, and if necessary install the right SIGINT
handler. */
class gdbpy_enter
However I've added some text to the constructor as well.
Tom
next prev parent reply other threads:[~2022-01-10 21:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 17:13 [PATCH 0/3] Improvements to Python parameters Tom Tromey
2022-01-05 17:13 ` [PATCH 1/3] Change how Python architecture and language are handled Tom Tromey
2022-01-10 15:35 ` Andrew Burgess
2022-01-10 21:15 ` Tom Tromey
2022-01-10 21:22 ` Tom Tromey [this message]
2022-01-05 17:13 ` [PATCH 2/3] Fix another crash with gdb parameters in Python Tom Tromey
2022-01-10 15:46 ` Andrew Burgess
2022-01-05 17:13 ` [PATCH 3/3] Add a way to temporarily set a gdb parameter from Python Tom Tromey
2022-01-10 15:59 ` Andrew Burgess
2022-01-10 21:16 ` 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=87zgo3l20n.fsf@tromey.com \
--to=tromey@adacore.com \
--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).