Chris@USC-ECLB.ARPA (Christopher Ho) (01/22/87)
I'm trying to use XDELTA to delve into some pseudo-device-driver- and ACP-level code I'm writing on a VaxStation II, but am having problems. At indeterminate times while single-stepping through my C ACP (using the normal VMS debugger) the VaxStation stops responding to the keyboard. The mouse still generates response, and I can use a terminal on the console line to login. If I use the console to generate a break, then set IPL to 5 (so XDELTA gains control), my OPA0: window opens up and I find the system doing: 80008B1F: brb 80008B1F This looks suspiciously like what I imagine the NULL process loop to be. It somehow seems that my keyboard interrupts (at presumably low priority) are being locked out. Does anyone have any idea what is going on here? I doubt there's a bug in my code, as there's so little of it so far. Maybe there's some interaction among XDELTA, the VMS debugger, the VWS software and/or my driver/ACP? Am I doing something that is, for some strange reason, "unsupported"? -------