One question reg this.
Will DbgPrint produce output even in FREE BUILD of the driver.
The behavior I noticed was, DbgView captured debug strings only from
DEBUG BUILD of my driver & not from FREE BUILD (code was same).
When they ship to customers, they used to ship FREE BUILD only, right?
Thanks,
Sathya
===================================
Knowledge, Skill and desire will lead to SUCCESS.
-----Original Message-----
From: Loren Wilton [mailto:xxxxx@earthlink.net]
Sent: Thursday, August 07, 2003 10:35 AM
Subject: Re: Debugging
We have a driver packaged into a product. It gets installed on
customer’s machine and sometimes things are
Not working. It could be due to some failure case in driver, but we
will
never know that unless we log those debug messages coming out of the
driver. So, I need to log those DbgPrint messages somewhere which the
customer could pass on to us and we can take a look at them. That’s why
I thought of implementing a scheme where we can put those debug
messages
to a file.
Get DbgView from SysInternals. Or OSR has something similar. If things
don’t work, just have you customer start dbgview, which will capture the
dbgprints, then they can save the text to a file and send it to you.
Works for me!
Loren
DbgPrint works in release builds too ! May be you have overseen that within the release builds, the DbgPrint define is replaced with
a dummy in your driver ? You should probably take a closer look into debugging and debug build internals. Obey rules without knowing
why they are there, is never recommended.
----- Original Message -----
From: “Sathyanarayanan Srinivasan”
To: “Windows System Software Developers Interest List”
Sent: Friday, August 08, 2003 6:21 AM
Subject: [ntdev] RE: Debugging
> One question reg this.
> Will DbgPrint produce output even in FREE BUILD of the driver.
> The behavior I noticed was, DbgView captured debug strings only from
> DEBUG BUILD of my driver & not from FREE BUILD (code was same).
> When they ship to customers, they used to ship FREE BUILD only, right?
>
> Thanks,
> Sathya
>
> ===================================
> Knowledge, Skill and desire will lead to SUCCESS.
> ===================================
>
>
> -----Original Message-----
> From: Loren Wilton [mailto:xxxxx@earthlink.net]
> Sent: Thursday, August 07, 2003 10:35 AM
> Subject: Re: Debugging
>
>
> >We have a driver packaged into a product. It gets installed on
> >customer’s machine and sometimes things are
> >Not working. It could be due to some failure case in driver, but we
> will
> >never know that unless we log those debug messages coming out of the
> >driver. So, I need to log those DbgPrint messages somewhere which the
> >customer could pass on to us and we can take a look at them. That’s why
> >I thought of implementing a scheme where we can put those debug
> messages
> >to a file.
>
> Get DbgView from SysInternals. Or OSR has something similar. If things
> don’t work, just have you customer start dbgview, which will capture the
> dbgprints, then they can save the text to a file and send it to you.
>
> Works for me!
>
> Loren
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@compaqnet.be
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>