Also add a script to grab stack traces of all on-CPU threads.
Details
Diff Detail
- Repository
- rG FreeBSD src repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
LGTM!
At work we have an extension that allows to dump (and save) both a text dump and a vmcore at the same time.
We use that to easily capture from ddb things that are hard (but not impossible) to get with kgdb.
The path you open here is a great alternative to that.
That's kind of neat. Note that there may be some ways to get kgdb to auto-load python scripts if you install them in the right path the way the scripts to create pretty-printers for libc++ works now. It may be worth looking at that at some point. That is, you would perhaps install a python script to /boot/kernel/kernel.py (or whatever gdb wants it called) during installkernel and then gdb (and kgdb) would auto-load it.
Note that you could store the "real" scripts in /usr/libexec/kgdb or the like and have the kernel-gdb.py just be a small script that loads the common ones.