Win2K SP1 Checked build bugchecks with too many DbgPrints?

I’m not sure where to submit this as a potential bug, maybe one of the MSFT
guys could tell me?

I have found that the full checked build of Win2K SP1 will repeatably
bugcheck if I issue a large number of DbgPrint() calls with a kernel
debugger hooked up. It works if I don’t hook up the debugger. It also
works on the Free build with or without a debugger hooked up. The Checked
OS works if I remove the DbgPrint() calls. I haven’t tried it with a
Checked kernel and/or HAL on the free build. I’m using the 2.0.11 debugging
tools, and I haven’t tried it with any other.

Phil

* Philip D. Barila | (503) 264-8386
* Intel Corp. | M/S JF2-53 Office JF2-2-G6
* Storage Architecture and Performance
* Internet Systems Lab


You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com