core file, much like 'netstat -anr' does it for living kernel.
Right now only AF_INET routing table is printed. AF_INET6 needs to
be done. But the most difficult part of the script (recursion!) is
complete.
Sponsored by: Nginx, Inc.
debugging kernels and kernel modules much easier. It will automaticly
locate kernel source, extract kernel module information, and rerun gdb
to load kernel module symbol information (if available by compiling module
w/ debuging symbols).
I have not run these recently, so may need to be updated to work with
gdb6. Feel free to fix as appropriate for -current.
Add new kldstat, kldstat-v and kernel macros. The kldstat macro is
functionally equivalent to the previous implementation, but it looks
prettier and it matches the kldstat-v macro better. kldstat-v gives
output similar to userland kldstat -v (note lacking space), and kernel
loads a new kernel and dump.
Submitted by: des
made any easier by the brain-damaged format required for the
documentation: one line, no full stops or commas.
Remove macro xy. I can't see any use for it any more.
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.
