Not having DbgPrint and KdPrint on WinDbg console

Hi,

Don’t know why but cant get DbgPrint and KdPrint on WinDbg console.

Can anyone give some ideas of what can be wrong?

Thanks,

Nuno

Are you enabling the prints http://www.osronline.com/article.cfm?id=295
You might want to try
http://www.osronline.com/article.cfm?article=537

Don Burn
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

xxxxx@imaginando.net” wrote in message
news:xxxxx@ntdev:

> Hi,
>
> Don’t know why but cant get DbgPrint and KdPrint on WinDbg console.
>
> Can anyone give some ideas of what can be wrong?
>
> Thanks,
>
> Nuno

Hi,

Thanks for the reply.

Can’t understand. I have already tried the two tools and putted a value of 15 in the box for default and the output still doesn’t come out.

Any ideas?

Nuno

Try !dbgprint on the windbg console

Nik Twerdochlib
Software Developer

+1.601.607.8309 O
+1.866.522.8678 F

BOMGAR | Enterprise Remote Support™

One of the Fastest-Growing Technology Companies in America | Technology Fast 500™

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@imaginando.net
Sent: Tuesday, April 10, 2012 6:25 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Not having DbgPrint and KdPrint on WinDbg console

Hi,

Don’t know why but cant get DbgPrint and KdPrint on WinDbg console.

Can anyone give some ideas of what can be wrong?

Thanks,

Nuno


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

Also, do you have the registry entry: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Debug Print Filter\DEFAULT set to 0xffffffff

Nik Twerdochlib
Software Developer

+1.601.607.8309 O
+1.866.522.8678 F

BOMGAR | Enterprise Remote Support™

One of the Fastest-Growing Technology Companies in America | Technology Fast 500™

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@imaginando.net
Sent: Tuesday, April 10, 2012 6:25 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Not having DbgPrint and KdPrint on WinDbg console

Hi,

Don’t know why but cant get DbgPrint and KdPrint on WinDbg console.

Can anyone give some ideas of what can be wrong?

Thanks,

Nuno


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

Hi,

I found the problem.

I was not setting the Debug Print Filter registry item on the target machine, but on the host machine.

Working already! :wink:

Thanks for your time and attention,

With my best regards,

Nuno Santos

Nik Twerdochlib wrote:

Try !dbgprint on the windbg console

As far as I can tell, that command is entirely decorative. It
apparently requires some kind of magic incantation that has not been
revealed to me.


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

When I’ve used it, it appears to dump some circular buffer, with no indication where the start point is.

John

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: 10 April 2012 17:28
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Not having DbgPrint and KdPrint on WinDbg console

Nik Twerdochlib wrote:

Try !dbgprint on the windbg console

As far as I can tell, that command is entirely decorative. It
apparently requires some kind of magic incantation that has not been
revealed to me.


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


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

Yup, that’s exactly what it does. I use it all the time to try to catch what
was going on before the crash when looking at a dump. You have to be a bit
skeptical due to it being a circular buffer, but it also includes the prints
before an ASSERT which can be handy when someone runs a checked build
without the debugger attached.

Note that on Vista and later the logging happens after the debug print
filter is applied, which is a bit of a bummer.

-scott


Scott Noone
Consulting Associate and Chief System Problem Analyst
OSR Open Systems Resources, Inc.
http://www.osronline.com

“John Hall” wrote in message news:xxxxx@ntdev…

When I’ve used it, it appears to dump some circular buffer, with no
indication where the start point is.

John

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: 10 April 2012 17:28
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Not having DbgPrint and KdPrint on WinDbg console

Nik Twerdochlib wrote:

Try !dbgprint on the windbg console

As far as I can tell, that command is entirely decorative. It
apparently requires some kind of magic incantation that has not been
revealed to me.


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


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

well with !dbgprint you can view the spew in both kernel debugger as
well as a local kernel debugging session

kd> !dbgprint

*******************************************************************************
*
* This is the string you add to your checkin description
* Driver Verifier: Enabled for cdo.sys on Build 2600 nlM2yDyCVdApG2zis97dQD
*
*******************************************************************************

lkd> !dbgprint

*******************************************************************************
*
* This is the string you add to your checkin description
* Driver Verifier: Enabled for cdo.sys on Build 2600 nlM2yDyCVdApG2zis97dQD
*
*******************************************************************************

no that is a real copy paste i did not edit kd into lkd by hand :slight_smile:

if you dont have kd attached and you didnt run debugview etc you
could still access 4kb of dbgspew using lkd use kdbgctrl to increase
more than 4kb

Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Tue Apr 10 23:39:11.032 2012 (UTC + 5:30)
System Uptime: 0 days 0:01:22.268
!dbgprint
ERROR: DavReadRegistryValues/RegQueryValueExW(4). WStatus = 5
ERROR: DavReadRegistryValues/RegQueryValueExW(5). WStatus = 5
ERROR: DavReadRegistryValues/RegQueryValueExW(6). WStatus = 5
Hello Tim You Can See me In Local Kernel Debugging even if You Didnt have DebugV
iew Running
Hello Tim You Can See me In Local Kernel Debugging even if You Didnt have DebugV
iew Running
Hello Tim You Can See me In Local Kernel Debugging even if You Didnt have DebugV
iew Running
lkd>

On 4/10/12, Scott Noone wrote:
> Yup, that’s exactly what it does. I use it all the time to try to catch what
> was going on before the crash when looking at a dump. You have to be a bit
> skeptical due to it being a circular buffer, but it also includes the prints
> before an ASSERT which can be handy when someone runs a checked build
> without the debugger attached.
>
> Note that on Vista and later the logging happens after the debug print
> filter is applied, which is a bit of a bummer.
>
> -scott
>
> –
> Scott Noone
> Consulting Associate and Chief System Problem Analyst
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
> “John Hall” wrote in message news:xxxxx@ntdev…
>
> When I’ve used it, it appears to dump some circular buffer, with no
> indication where the start point is.
>
> John
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
> Sent: 10 April 2012 17:28
> To: Windows System Software Devs Interest List
> Subject: Re: [ntdev] Not having DbgPrint and KdPrint on WinDbg console
>
> Nik Twerdochlib wrote:
>> Try !dbgprint on the windbg console
>
> As far as I can tell, that command is entirely decorative. It
> apparently requires some kind of magic incantation that has not been
> revealed to me.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> 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
>
>
> —
> 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
>