I've now got windbg working on my host system. I confirm that it can break into the target in normal usage, because the target computer stops responding until I hit F5on the host to resume the target.
However, when I run my program to test my driver, the target freezes, as I have reported before on NTDEV a few times.
Unfortunately, the Break command in windbg also fails to do anything.
So my basic question for you all is this:
* What are possible things that could be going on so that the debugger cannot break into the target? And what could I do to see what is happening just before the freeze or even during the freeze? Does windbg have a command that will cause a bugcheck on the target, or would this command fail to work too.
Do you think it would help if I wire an external switch to the NMI input on my CPU?
I'll repost this on WINDBG list as soon as my joining of that list is processed.