Stefan Hajnoczi <stefa...@redhat.com> writes: > The scripts/qemu-gdb.py file is not easily discoverable. Add a .gdbinit > file so GDB either loads qemu-gdb.py automatically or prints a message > informing the user how to enable them (some systems disable ./.gdbinit > loading for security reasons). > > Suggested-by: Eric Blake <ebl...@redhat.com> > Signed-off-by: Stefan Hajnoczi <stefa...@redhat.com> > --- > .gdbinit | 8 ++++++++ > 1 file changed, 8 insertions(+) > create mode 100644 .gdbinit > > diff --git a/.gdbinit b/.gdbinit > new file mode 100644 > index 0000000..9d322fc > --- /dev/null > +++ b/.gdbinit > @@ -0,0 +1,8 @@ > +# GDB may have ./.gdbinit loading disabled by default. In that case you can > +# follow the instructions it prints. They boil down to adding the following > to > +# your home directory's ~/.gdbinit file: > +# > +# add-auto-load-safe-path /path/to/qemu/.gdbinit > + > +# Load QEMU-specific sub-commands and settings > +source scripts/qemu-gdb.py
While this works well enough you might as well just comment the helper script itself. Would this script take precedence over a users ~/.gdbinit? How would it work for out-of-tree builds? GDB does have a mechanism for autoloading extensions by way of adding ELF sections: https://sourceware.org/gdb/current/onlinedocs/gdb/dotdebug_005fgdb_005fscripts-section.html#dotdebug_005fgdb_005fscripts-section -- Alex Bennée
