- Re: boot.ini set for debugging, system performance
- Posted by Farooque Khan on September 27th, 2003
Not sure about debugger enabled boot, but IMHO drivers which do
a DbgPrint will continue to do so whether /debug switch is
specified or not. So that won't make a difference in system performance.
--
-Farooque Khan
http://www.concretioindia.com
"Daniel" <daniel__steve@hotmail.com> wrote in message
news:008a01c3844a$522db780$a401280a@phx.gbl...
- Posted by Maxim S. Shatskih on September 27th, 2003
DbgPrint will be a no-op if there is no active kernel debugger attached.
/debug only allows monitoring for active kernel debugger, it does not says that
the debugger is active.
--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com
"Farooque Khan" <farooquek-at-concretioindia-dot-com> wrote in message
news:eJ6mq0KhDHA.1800@TK2MSFTNGP09.phx.gbl...
- Posted by James Antognini on September 27th, 2003
I'm not sure I understand what you're saying. I just ran a driver of mine that does
DbgPrint. It is running on a system without an attached debugger (namely, nothing
in the chosen boot.ini entry with /debug, /debutport or the like). I could see the
messages via DebugView from Sysinternals. Now maybe DebugView makes things look as
though a debugger is attached, but surely even without DebugView running, there is
some handling in whatever DbgPrint calls before the message is discarded. It is
surely not a no-op.
Maybe you were think about the common practice of turning the DbgPrint macro into a
no-op if the build doesn't have the DBG preprocessor variable defined?
"Maxim S. Shatskih" wrote:
--
If replying by e-mail, please remove "nospam." from the address.
James Antognini
Windows DDK MVP
