not the intention.
Rearrange "you may want to change these values" values to the top, and
reduce their number as much as possible.
tr macro: Require a parameter (because gdb is too stupid to understand
optional parameters), and create macros tr0, tr1 and trf which call it
to connect to /dev/cuaa0, /dev/cuaa1 and firewire connections
respectively.
Split kld symbol load into two separate macros: revision 1.5
simplified things for the /dev/mem case, but broke it for anything
else. Now the simple /dev/mem version is called kldsyms, and the
version for serial debugging and processor dumps is called getsyms,
and still requires this irritating cut and paste.
Change comments on startup to make life easier for the poor
(de)bugger.
no matter where in the directory structure it may be. Use this and the "-k"
flag in the generated gdbinit files so that the "getsyms" function in gdb
requires no user intervention to run and will find every module if they're
in the kernel build's module directory. This is still quite useful for
cases where gdb knows that the path for some modules is /boot/kernel and
others are in the object directory for /usr/src/sys/$ARCH/compile/kernel.
Approved by: grog
so it needs to be (and can be) specified on the command line. Don't
try to automatically connect to a remote machine, so that the same
.gdbinit file can be used for analysing processor dumps.
