From 1178f01adf9c3b3a5b0fa564aa4d570e26a26819 Mon Sep 17 00:00:00 2001 From: Andrew Burgess Date: Wed, 26 Aug 2020 17:31:12 +0100 Subject: 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/top.c | 6 ------ 1 file changed, 6 deletions(-) (limited to 'gdb/top.c') diff --git a/gdb/top.c b/gdb/top.c index b58cd4f..a83d16b 100644 --- a/gdb/top.c +++ b/gdb/top.c @@ -2408,12 +2408,6 @@ gdb_init () set_language (language_c); expected_language = current_language; /* Don't warn about the change. */ - /* Python initialization, for example, can require various commands to be - installed. For example "info pretty-printer" needs the "info" - prefix to be installed. Keep things simple and just do final - script initialization here. */ - finish_ext_lang_initialization (); - /* Create $_gdb_major and $_gdb_minor convenience variables. */ init_gdb_version_vars (); } -- cgit v1.1