swiftgri...@gmail.com (Swift Griggs) writes:
>Next time it happens, I'll pay attention and expand the kernel threads to
>see which one is doing it. I guess there is no way to do a gdb 'attach' to
>the kernel thread to get a backtrace, though. I'm assuming one has to do
>this sort of thing with a specialized kernel debuggger/profiler.
And there is. You can use either use ddb(4) or crash(8) to get backtraces
from a thread, including a kernel thread. Use 'ps' to print the process
table which shows each LWP address, then 'bt/a' with the address of the
thread you want to see.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
