Check gdb_python_module in gdbpy_handle_missing_debuginfo

If you run gdb in the build tree without --data-directory, on a
program that does not have debug info, it will crash, because
gdbpy_handle_missing_debuginfo unconditionally uses gdb_python_module.

Other code in gdb using gdb_python_module checks it first and it
seemes harmless to do the same thing here.  (gdb_python_initialized
does not cover this case so that python can be partially initialized
and still somewhat work.)

diff --git a/gdb/python/python.c b/gdb/python/python.c
index 4523e30ed249efe3936e16d08e8681d377f4ed89..7e48165db21abd3f4717e786f454ea90db788b1d 100644 (file)
--- a/gdb/python/python.c
+++ b/gdb/python/python.c
@@ -1703,7 +1703,7 @@ gdbpy_handle_missing_debuginfo (const struct extension_language_defn *extlang,
                                struct objfile *objfile)
 {
   /* Early exit if Python is not initialised.  */
-  if (!gdb_python_initialized)
+  if (!gdb_python_initialized || gdb_python_module == nullptr)
     return {};
 
   struct gdbarch *gdbarch = objfile->arch ();