LEAF vkernel support update 13-May-2008

[Matthew Dillon]

:Great, used it to reproduce a bug I'm hitting on my box. Just run initvkernel,
:and then (pasting from my scrollback buffer)
:
:..
:aggelos 74216     1  0.0  0.4 1052872 4480  p4  TXL+  5:20AM   0:00.01 /build/home/agge  2042 74216 74113   0 152   0 1052872 4480 umtxsl TXL+  p4    0:00.01 /build/home/aggelos/vkernel/kernel -m 64m -i /home/aggelos/build/vkernel/memimg.01 -r /home/aggelos/build/vkernel/rootimg.01 -r /home/aggelos/build/vkernel/swapimg.01
:aggelos 74216     0  0.0  0.4 1052872 4480  p4  TXL+  5:20AM   0:00.25 /build/home/agge  2042 74216 74113   0 152   0 1052872 4480 stop   TXL+  p4    0:00.25 /build/home/aggelos/vkernel/kernel -m 64m -i /home/aggelos/build/vkernel/memimg.01 -r /home/aggelos/build/vkernel/rootimg.01 -r /home/aggelos/build/vkernel/swapimg.01
:leaf:/home/aggelos> kill 74216
:leaf:/home/aggelos> kill -9 74216
:leaf:/home/aggelos> kill -9 74216
:
:(notice, no ESRCH)
:
:Is this a known bug?
:
:TIA,
:Aggelos

    gdb has a real hard time with threaded programs.  The vkernel isn't
    stuck, it's in a stopped state under the control of gdb.  All you can
    do at that point is kill gdb, and then the vkernel will die too.

    This is primarily a bug with our lack of gdb support for debugging
    threaded programs, but I'm sure there are some procfs issues too.
    I've never been able to reliably set a break point with gdb on a
    vkernel.

					-Matt
					Matthew Dillon 
					<dillon at backplane.com>