gdb: initialise extension languages after processing early startup files
authorAndrew Burgess <andrew.burgess@embecosm.com>
Wed, 26 Aug 2020 16:31:12 +0000 (17:31 +0100)
committerAndrew Burgess <andrew.burgess@embecosm.com>
Wed, 28 Apr 2021 08:56:20 +0000 (09:56 +0100)
commit1178f01adf9c3b3a5b0fa564aa4d570e26a26819
tree6a3c5a423e9cc2bd7d84a6ef34a69b7eee610c67
parent880ae75a2b7106045ed2ae212bbc28e4dc0ad667
gdb: initialise extension languages after processing early startup files

Now (thanks to the last few commits) all extension languages are
fully initialised in their finish_initialization method, this commit
delays the call to this method until after the early initialization
files have been processed.

Right now there's no benefit from doing this, but in a later commit I
plan to add new options for Python that will control how Python is
initialized.

With this commit in place, my next commits will allow the user to add
options to their early initialization file and alter how Python starts
up.

There should be no user visible changes after this commit.

gdb/ChangeLog:

* main.c (captured_main_1): Add a call to
finish_ext_lang_initialization.
* top.c (gdb_init): Remove call to finish_ext_lang_initialization.
gdb/ChangeLog
gdb/main.c
gdb/top.c
This page took 0.030484 seconds and 4 git commands to generate.