Re: [PATCH 3/3] gdb/python: add gdbpy_register_subsystem mechanism

[Tom Tromey <tom@tromey.com>]

>>>>> "Andrew" == Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org> writes:

Andrew> All callbacks registered through gdbpy_register_subsystem are added to
Andrew> a vector, and in python.c we iterate over the vector and all the
Andrew> various functions as needed.

Andrew> The only question is when should gdbpy_register_subsystem be called?
Andrew> The answer I think is to make use of GDB's existing _initialize_*
Andrew> function mechanism.  A few of the python sub-system files already
Andrew> include an _initialize_* function, but most needed to have one added.

This approach seems a little weird to me, in that it uses the
_initialize_* functions to hook into gdb's existing initialization
approach, but then registers a second layer of initialization functions
in a vector to be called a little later.

What if, instead, something like make-init-c was used, but specifically
for Python initialization (and finalization) functions?

Tom