933785a027
crash dumps with kernel modules. The command is basically a wrapper around add-symbol-file except that it uses the kernel linker data structures and the ELF section headers of the kld to calculate the section addresses add-symbol-file needs. The 'kld' parameter may either be an absolute path or a relative path. kgdb looks for the kld in several locations checking for variants with ".symbols" or ".debug" suffixes in each location. The first location it tries is just opening the specified path (this handles absolute paths and looks for the kld relative to the current directory otherwise). Next it tries to find the module in the same directory of the kernel image being used. If that fails it extracts the kern.module_path from the kernel being debugged and looks in each of those paths. The upshot is that for the common cases of debugging /boot/kernel/kernel where the module is in either /boot/kernel or /boot/modules one can merely do 'add-kld foo.ko'. MFC after: 1 week |
||
|---|---|---|
| .. | ||
| kgdb.1 | ||
| kgdb.h | ||
| kthr.c | ||
| main.c | ||
| Makefile | ||
| trgt_amd64.c | ||
| trgt_arm.c | ||
| trgt_i386.c | ||
| trgt_ia64.c | ||
| trgt_powerpc.c | ||
| trgt_sparc64.c | ||
| trgt.c | ||