Hi all,
I am new to windows drivers and can’t find very good information. I am unable to see a kdprint statement. I have windbg on my m/c. My code has kdprint statements and is built as a checked build. What else do I need to do to see the results? Are there any good tutorials to hold my hand through the basic process? I am able to load the driver but can’t see a simple kdprint statement using windbg.
Regards,
Nilam
What is the OS you are using? Is it Vista/Win2008? If so, you have to set
DebugPrintFilter keys in registry. Have a look on the following articles,
http://www.osronline.com/article.cfm?article=295
http://blogs.msdn.com/doronh/archive/2006/11/14/where-did-my-debug-output-go-in-vista.aspx
Regards,
T.V.Gokul.
On Wed, Jun 17, 2009 at 5:20 PM, wrote:
> Hi all,
>
> I am new to windows drivers and can’t find very good information. I am
> unable to see a kdprint statement. I have windbg on my m/c. My code has
> kdprint statements and is built as a checked build. What else do I need to
> do to see the results? Are there any good tutorials to hold my hand through
> the basic process? I am able to load the driver but can’t see a simple
> kdprint statement using windbg.
>
> Regards,
> Nilam
>
> —
> 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
>
I am using Windows XP SP3. So is it that I have to set DebugPrintFilter keys in registry for this OS?
Regards,
Nilam
Are you trying to use LiveKd, if so forget it and get a second system.
–
Don Burn (MVP, Windows DDK)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
wrote in message news:xxxxx@ntdev…
>I am using Windows XP SP3. So is it that I have to set DebugPrintFilter
>keys in registry for this OS?
>
> Regards,
> Nilam
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4162 (20090617)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
Information from ESET NOD32 Antivirus, version of virus signature database 4162 (20090617)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
What is your debugging system? You should be running WinDbg on a host
connected to a target via a 1394 cable. You can also use serial. There are a
couple of tools, the best one found on OsrOnline.com, that allow you to view
output to the WinDbg command window on a single system. However, that is NOT
a debugger tool, and if you insist on using it without WinDbg, good luck.
The personal opinion of
Gary G. Little
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@tcs.com
Sent: Wednesday, June 17, 2009 6:51 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Windbg kdprint
Hi all,
I am new to windows drivers and can’t find very good information. I am
unable to see a kdprint statement. I have windbg on my m/c. My code has
kdprint statements and is built as a checked build. What else do I need to
do to see the results? Are there any good tutorials to hold my hand through
the basic process? I am able to load the driver but can’t see a simple
kdprint statement using windbg.
Regards,
Nilam
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
Yes I am able to see the debug messages ( kdprint ) using DebugView utility.
Regards,
Nilam
You can’t see kdprint statements in “realtime” in a local windbg session. You have to use the command !dbgprint if windbg is running locally. But this is not very useful – as Don and Gary said, you need to have a setup with a second computer. The windbg help explains how to do this in the Kernel-Mode Setup section.