I was running the snv_22 kernel on a 32-bit x86 box under kmdb control,
with a breakpoint at bind_node+15, like this
bind_node+15:b <ebx::devinfo
,20:c
Now, as soon as we hit the breakpoint (e.g. because devfsadm is startetd),
a lot of output is printed to the screen and kmdb's built-in pager
"More [<space>, <cr>, q, n, c, a]" is activated.
I pressed the 'a' key .... and kmdb enters a strange state: kmdb
is stuck at the bind_node+15 breakpoint. It isn't possible to ::step,
::step over or ::continue from the bind_node+15 instruction. Even
after deleting the breakpoint and a ::continue command kmdb
insists that we have stopped at bind_node+15. The only way out
is to abort the debug session with "$q" and reboot the kernel.
<space>, <cr>, q, n, and c at the pager prompt work just fine.
Only 'a' doesn't work as expected.
This is not the expected behaviour, isn't it?
This message posted from opensolaris.org
