DebugMon question

I was wondering if DebugMon utility displays the DebugPrints/Trace output only with the debug version of the driver or with the release version too?

I would assume only debug version, but just wanted to double-check.

Thanks,
Vidya

It displays any DebugPrint output, so the answer depends on how the driver
is written. The macros that wrap debugprint are conditionalized by DBG, but
the function can be called from any build type.

I frequently use debug prints in released drivers to note really bad errors
or other unusual conditions.

Mark Roddy

On Thu, Sep 2, 2010 at 6:18 PM, Dharmaraju, Vidyadhari <
xxxxx@intel.com> wrote:

I was wondering if DebugMon utility displays the DebugPrints/Trace output
only with the debug version of the driver or with the release version too?

I would assume only debug version, but just wanted to double-check.

Thanks,
Vidya


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

It will do it for both the debug and the release version for DbgPrint,
of course KdPrint is a macro that expands to nothing for the release
version so you get no output with those.

Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

“Dharmaraju, Vidyadhari” wrote in
message news:xxxxx@ntdev:

> I was wondering if DebugMon utility displays the DebugPrints/Trace output only with the debug version of the driver or with the release version too?
>
> I would assume only debug version, but just wanted to double-check.
>
> Thanks,
> Vidya

Dharmaraju, Vidyadhari wrote:

I was wondering if DebugMon utility displays the DebugPrints/Trace output only with the debug version of the driver or with the release version too?

I would assume only debug version, but just wanted to double-check.

That depends on your driver. If you use KdPrint, that’s a macro that
disappears in a free build. If you call DbgPrint directly, that always
prints, no matter what build.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.