Make 'import gdb.events' work
authorTom Tromey <tromey@adacore.com>
Fri, 3 Jun 2022 13:59:49 +0000 (07:59 -0600)
committerTom Tromey <tromey@adacore.com>
Tue, 5 Jul 2022 16:28:39 +0000 (10:28 -0600)
commit3acd9a692ddaf8f24d6d34cb5ccb7c26d057e9b3
tree19216ecf8b1235823b9251f84710982be599e5f8
parent736918239b16cc2ff57bfc64a982f2f0afc8c0f6
Make 'import gdb.events' work

Pierre-Marie noticed that, while gdb.events is a Python module, it
can't be imported.  This patch changes how this module is created, so
that it can be imported, while also ensuring that the module is always
visible, just as it was in the past.

This new approach required one non-obvious change -- when running
gdb.base/warning.exp, where --data-directory is intentionally not
found, the event registries can now be nullptr.  Consequently, this
patch probably also requires

    https://sourceware.org/pipermail/gdb-patches/2022-June/189796.html

Note that this patch obsoletes

    https://sourceware.org/pipermail/gdb-patches/2022-June/189797.html
gdb/python/lib/gdb/__init__.py
gdb/python/py-evtregistry.c
gdb/python/py-evts.c
gdb/python/python-internal.h
gdb/python/python.c
gdb/testsuite/gdb.python/py-events.exp