Ah, that's it, I guess. Machine was not (for some reason) booted /debug.
....................dave
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Drew Bliss
Sent: Monday, May 08, 2006 3:13 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] dumping dbgprint buffer in a memory dump?
Was the machine booted /debug? That's necessary for any dbgprint output
to be accumulated.
If so, try x nt!KdPrint*.
KdPrintCircularBuffer is a pointer to the base of the current dbgprint
buffer (should point at KdPrintDefaultCircularBuffer on a default
system).
KdPrintBufferSize is the size of the current buffer.
KdPrintWritePointer is the next place to write.
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Dave Beaver
Sent: Monday, May 08, 2006 3:08 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] dumping dbgprint buffer in a memory dump?
Thanks, Drew, I didn't think I was completely nuts - but you can never
be too sure. This machine is bog standard Win2k3R2, 64bit enterprise,
with our driver code installed on it (filesystem and filter).
db nt!KdPrintDefaultCircularBuffer gives me lots of zeros (this claims
to be a complete memory dump).
2: kd> db nt!KdPrintDefaultCircularBuffer L4096
fffff80001194670 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ fffff80001194680 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
................
fffff80001194690 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ fffff800011946a0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
................
fffff800011946b0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ fffff800011946c0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
................
fffff800011946d0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 ................ fffff800011946e0 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
................
... and so on, all zeros.
I doubt this machine has had zero dbgprints since it started up, as it
was running our rather chatty product (debug version) when it crashed -
but I suppose that's possible. I will play around with this and see if
there's anything obvious that I missed here.
....................dave
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Drew Bliss
Sent: Monday, May 08, 2006 2:46 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] dumping dbgprint buffer in a memory dump?
It should work fine. Have you used kdbgctrl to modify where your
dbgprint buffer is? If not the raw data should be in
nt!KdPrintDefaultCircularBuffer (default 4K of char on a release build).
Does it look valid?
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Dave Beaver
Sent: Monday, May 08, 2006 2:38 PM
To: Kernel Debugging Interest List
Subject: [windbg] dumping dbgprint buffer in a memory dump?
I feel really dumb asking this, but I'm almost certain I've made this
work in the past; I need to dump the dbgprint buffer in a complete
memory dump. I recall just using the !dbgprint command to do this (this
was a few years ago), but trying it today (with the latest windbg bits)
just does not seem to work on my 64-bit machine (!dbgprint works,
apparently, but it prints a very short random line). Am I being
delirious (has this not worked in the past, and I'm nuts?) or is this
something that doesn't work (it seems too universally useful for that to
be the case), or is this a DFU issue?
thanks............dave
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