summaryrefslogtreecommitdiffstats
path: root/sys/vm/vm_object.c
diff options
context:
space:
mode:
authormarcel <marcel@FreeBSD.org>2004-07-25 05:29:15 +0000
committermarcel <marcel@FreeBSD.org>2004-07-25 05:29:15 +0000
commit79ca58867f1261b0d00ab949823fdd2194f1962a (patch)
tree9787cff5df31a58638670470d7cbe3eed646ca9e /sys/vm/vm_object.c
parentc2fb7a1b2d400005d0b0f79f0850761a1b24dfe8 (diff)
downloadFreeBSD-src-79ca58867f1261b0d00ab949823fdd2194f1962a.zip
FreeBSD-src-79ca58867f1261b0d00ab949823fdd2194f1962a.tar.gz
Add the beginnings of kernel debugging support. the kgdb(1) tool
is basicly a shell on top of libgdb that knows about kernel threads, kernel modules and kvm(3). As the word "beginnings" implies, not all of the features have been implemented yet. The tool is useful and I'd like feedback on the taken route. The simplest way to debug a kernel core file is: kgdb -n 0 This opens /var/crash/vmcore.0 with the corresponding kernel in the object directory (kernel.debug is used if it exists). Typical things that need to be added are: o Auto loading of kernel modules, o Handling of trapframes so that backtraces can be taken across them, o Some fancy commands to extract useful information out of a core file, o Various (probably many) other things.
Diffstat (limited to 'sys/vm/vm_object.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud