From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/7] gdb: delay python initialisation until gdbpy_finish_initialization
Date: Fri, 23 Apr 2021 08:26:40 -0600 [thread overview]
Message-ID: <87zgxp6pr3.fsf@tromey.com> (raw)
In-Reply-To: <222490f5330bee284b46010719040df190b7631a.1619125261.git.andrew.burgess@embecosm.com> (Andrew Burgess's message of "Thu, 22 Apr 2021 22:02:44 +0100")
>>>>> "Andrew" == Andrew Burgess <andrew.burgess@embecosm.com> writes:
Andrew> Delay Python initialisation until gdbpy_finish_initialization.
Andrew> This is mostly about splitting the existing gdbpy_initialize_*
Andrew> functions in two, all the calls to register_objfile_data_with_cleanup,
Andrew> gdbarch_data_register_post_init, etc are moved into new _initialize_*
Andrew> functions, but everything else is left in the gdbpy_initialize_*
Andrew> functions.
Andrew> Then the call to do_start_initialization (in python/python.c) is moved
Andrew> from the _initialize_python function into gdbpy_finish_initialization.
Looks good, thank you.
Tom
next prev parent reply other threads:[~2021-04-23 14:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 21:02 [PATCH 0/7] New options to control how Python is initialized Andrew Burgess
2021-04-22 21:02 ` [PATCH 1/7] gdb: remove unused argument from gdb_init Andrew Burgess
2021-04-23 14:15 ` Tom Tromey
2021-04-22 21:02 ` [PATCH 2/7] gdb: ensure SIGINT is set to SIG_DFL during initialisation Andrew Burgess
2021-04-23 14:16 ` Tom Tromey
2021-04-22 21:02 ` [PATCH 3/7] gdb: delay python initialisation until gdbpy_finish_initialization Andrew Burgess
2021-04-23 14:26 ` Tom Tromey [this message]
2021-04-22 21:02 ` [PATCH 4/7] gdb delay guile initialization until gdbscm_finish_initialization Andrew Burgess
2021-04-23 14:29 ` Tom Tromey
2021-04-22 21:02 ` [PATCH 5/7] gdb: initialise extension languages after processing early startup files Andrew Burgess
2021-04-23 14:30 ` Tom Tromey
2021-04-22 21:02 ` [PATCH 6/7] gdb: extension languages finish_initialization to initialize Andrew Burgess
2021-04-23 14:31 ` Tom Tromey
2021-04-22 21:02 ` [PATCH 7/7] gdb: startup commands to control Python extension language Andrew Burgess
2021-04-23 10:31 ` Eli Zaretskii
2021-04-23 14:32 ` Tom Tromey
2021-04-29 8:32 ` Tom de Vries
2021-04-29 9:35 ` Andrew Burgess
2021-04-29 9:46 ` Andrew Burgess
2021-04-29 10:08 ` Tom de Vries
2021-05-02 10:31 ` Andrew Burgess
2021-05-02 18:15 ` Tom de Vries
2021-04-29 12:17 ` Eli Zaretskii
2021-04-29 12:32 ` Eli Zaretskii
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=87zgxp6pr3.fsf@tromey.com \
--to=tom@tromey.com \
--cc=andrew.burgess@embecosm.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).