Some gflags settings require /debug and some don’t, I’m not sure if
there’s a master list somewhere or not. In general
kernel-debugging-related things will require /debug.
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Arosh
Sent: Wednesday, October 25, 2006 10:49 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] !DBGPRINT- buffer DbgPrint, does it work ?
Sorry, I didn’t try that yet. I did not knew that gflags setting
requires a /debug run, is that required for all gflags settings ?
(sorry, I’m a newbie, I didn’t see it mentioned in the docs ) ,
I’ll give it a try.
Thanks again.
b.t.w.
nt!KdPrintWritePointer point to a pointer same as
8069a000 nt!KdPrintCircularBuffer
which is a zeroed block
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Drew Bliss
Sent: Wednesday, October 25, 2006 7:14 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] !DBGPRINT- buffer DbgPrint, does it work ?
That’s the expected output, it shows the addresses of the symbols. You
then need to dd those addresses to see that actual memory content.
However, you mention that you’re booting /nodebug, in which case the
DbgPrint logging is turned off since all debugging is disabled. Does it
work if you boot /debug?
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Arosh
Sent: Wednesday, October 25, 2006 1:44 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] !DBGPRINT- buffer DbgPrint, does it work ?
Hey Drew and all,
This is what I got
1: kd> x nt!kdprint*
8069b000 nt!KdPrintWritePointer =
8069a000 nt!KdPrintCircularBuffer =
8069b004 nt!KdPrintRolloverCount =
Is that the address of the buffer? if so it is empty!
can any one think of a reason for that? (it’s a checked version(my
drivers) ,b.t.w. full crash dump, and /nodebug boot)( should I use
DbgPrintEx instead ?)
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Drew Bliss
Sent: Tuesday, October 24, 2006 9:17 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] !DBGPRINT- buffer DbgPrint, does it work ?
You’re running it against a dump file, correct? What kind of dump file
is it? Minidumps won’t have the information.
If this is a larger dump the buffer should be there. Try x nt!kdprint*
and see if the buffers referred to exist and are readable.
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Arosh
Sent: Tuesday, October 24, 2006 3:17 AM
To: Kernel Debugging Interest List
Subject: [windbg] !DBGPRINT- buffer DbgPrint, does it work ?
Hi All,
The extension !dbgprint doesn’t work for me (no error return, nothing).
I did set with GFLAGS & restart and checked after that(in GFLAGS) that
it is still set (buffer DbgPring), any one can think of a reason ?
The machine I set the flag on and I’m doing a crash dump analysis is XP.
And I’m using WinDbg:6.6.0003.5 on an XP to do so.
Thanks,
Daniel.
xxxxx@gmail.com
I’m quite new (or you can say old and very rusty) so I’m sorry if I’ll
be asking stupid question evry ones in a while (-; thanks
Get the latest news on SurfControl and our products,
subscribe to our monthly e-newsletter, SurfAdvisory at:
http://www.surfcontrol.com/resources/surfadvisory/surfadvisory_signup.as
px
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, distribution or any action taken
or omitted to be taken in reliance on it, is prohibited and may be
unlawful. If you believe that you have received this email in error,
please contact the sender.
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to windbg as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com