A better support of LArSoft in gdb

[gennadiy-fnal]

We (Icarus and SBND) need a couple of features added to LArSoft, primarily to speed up the debugging of LArSoft packages deployed with Spack using gdb:

1. an automated way to remap paths of the compiled source code to the actual location of installed sources, e.g. using the set substitute-path "{from_path}" "{to_path}" command, so GDB displays source code in the TUI window.

2. gdb macros for printing a nice summary about an art event, such as its number, list of products and their IDs, etc. This would really help with debugging the experiment's analyzer code.

3. an option to include gdb as a dependency for the art product suite, e.g. '+gdb', with TUI and DAP features enabled.

4. a tutorial on how to use these features effectively.

[knoepfel]

Hi @gennadiy-fnal, thank you for the note. Such facilities would be helpful, but right now the SciSoft team does not have the effort to provide them. As always, we invite contributions from others who have the time and interest to pursue such ideas.