I saved my breakpoints to a file, then in a new session, "source"d the file to recreate them. However, they weren't recreated, because I had neglected to "set breakpoint pending on": (gdb) source /tmp/B Function "nsDOMWindowUtils::SendMouseEventCommon" not defined. Make breakpoint pending on future shared library load? (y or [n]) [answered N; input not from terminal] No source file named EventBinding.cpp. Make breakpoint pending on future shared library load? (y or [n]) [answered N; input not from terminal] One way around this would be to arrange for this to be handled explicitly in the saved script.
Maybe a "-pending" flag could be added to the "break" command for this.
The 'save' command could now emit: with breakpoint pending on -- break ...
I have a patch now.
The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2d06834a961f42671c72a409aaff278ea58d6e5c commit 2d06834a961f42671c72a409aaff278ea58d6e5c Author: Tom Tromey <tom@tromey.com> Date: Sun Jan 22 21:43:59 2023 -0700 Save breakpoints so they are automatically pending PR breakpoints/18183 points out that breakpoints saved with the "save breakpoints" command can be slightly inconvenient, depending on "set breakpoint pending". This patch makes use of the new "with" command to save breakpoints such that they will automatically be made pending, if necessary, when being restored. Unfortunately, reloading a breakpoint saved this way will also print: No symbol table is loaded. Use the "file" command. This seems strange to me, and also a bit useless, but changing create_breakpoint not to call exception_print in the AUTO_BOOLEAN_TRUE case caused other regressions, so I've left it as-is for the time being. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=18183 Reviewed-By: Keith Seitz <keiths@redhat.com>
Fixed.