I haven’t seen any reports of this come in. Can you attach a debugger
to the debugger, repro the exception, and send a minidump to
xxxxx@microsoft.com?
Jason
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Wednesday, August 24, 2005 6:43 AM
To: Kernel Debugging Interest List
Subject: Re: [windbg] Accessing PTEs in windbg/kd
J:
I haven’t looked at the dump you included closely, but I believe that
it is the same error that a number of us have been getting from
!ptov/!vtop in multiple versions of WinDbg, running under native OS’s,
so I don’t think that this is due to VMWare. I have researched this
issue fairly extensively and have been unable to resolve it by any means
other than reinstalling Windows. I imagine it has to due with the
version of DbgEng.DLL, but uninstalling WinDbg does not solve this
problem (WFP?).
MM
>> xxxxx@yahoo.co.uk 8/24/2005 7:18:32 AM >>>
Hi guys. I’ve been trying to examine the virtual<–>physical memory
mapping for a process using windbg.
As per the documentation, I try:
!process 0 0 to get the directory base for the process I am interested
in, from this remove 3 trailing zeros to get the page frame number:
e.g.
kd> !ptov d187
c0000094 Exception in kdexts.ptov debugger extension.
PC: 016f584a VA: 00000000 R/W: 1003f Parameter: 00000000
In fact any of the page table commands seem to fail, !vtop fails with:
Cannot find HARDWARE_PTE
I checked the lists for this, someone posted a similar issue in the
past but it was never resolved. I’ve tested this on both windbg/kd
current and an older version. I am debugging a XP SP1 VMware image -
could this be a VMWare related issue?
Cheers
J
To help you stay safe and secure online, we’ve developed the all new
Yahoo! Security Centre.
You are currently subscribed to windbg as: xxxxx@evitechnology.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com