dt command in crash dump analysis

WINDBG
1

My minidump file contains data for these memory regions
(displayed by cdb -v):

Memory regions: 15
0: ?000000007c93eb14? - ?000000007c93ec13?
1: ?00000000010c0000? - ?00000000010d3c4f?
2: ?00000000010d4000? - ?00000000010d4038?
3: ?000000000006fac4? - ?000000000006ffff?
4: ?00000000005cfd7c? - ?00000000005cffff?
5: ?000000000060fab4? - ?000000000060ffff?
6: ?000000000074fec4? - ?000000000074ffff?
7: ?00000000008dfdfc? - ?00000000008dffff?
8: ?000000000091fdec? - ?000000000091ffff?
9: ?000000000095fdf8? - ?000000000095ffff?
10: ?000000000099fed4? - ?000000000099ffff?
11: ?00000000009d95fc? - ?00000000009dffff?
12: ?0000000000a1fdf8? - ?0000000000a1ffff?
13: ?0000000000a7fdfc? - ?0000000000a7ffff?
14: ?0000000000abfed4? - ?0000000000abffff?
Total memory region size ?00000000`0001c259?

Issuing a dt command for a static variable with this declaration:

struct CmdLine {
int tConsoleApp;
int tNoKernelFs;
int tInstallService;
char * szServiceExePath;
int tRunAsReadOnly;
};
CmdLine cmdLine;

I get this output:

0:008> dt -v App!cmdLine
Got address 010c2068 for symbol
struct CmdLine, 5 elements, 0x14 bytes
+0x000 tConsoleApp : 0
+0x004 tNoKernelFs : 0
+0x008 tInstallService : 0
+0x00c szServiceExePath : (null)
+0x010 tRunAsReadOnly : 0

CDB found, that cmdLine is stored at 010c2068.
According to the region list, 010c2068 is *not* contained in the
dump.

My question:
Why displays the debugger values for the components of cmdLine?

2

This region contains 10c2068.

1: ?00000000010c0000? - ?00000000010d3c4f?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Albrecht Frenzel
Sent: Thursday, July 13, 2006 7:45 AM
To: Kernel Debugging Interest List
Subject: [windbg] dt command in crash dump analysis

My minidump file contains data for these memory regions (displayed by
cdb -v):

Memory regions: 15
0: ?000000007c93eb14? - ?000000007c93ec13?
1: ?00000000010c0000? - ?00000000010d3c4f?
2: ?00000000010d4000? - ?00000000010d4038?
3: ?000000000006fac4? - ?000000000006ffff?
4: ?00000000005cfd7c? - ?00000000005cffff?
5: ?000000000060fab4? - ?000000000060ffff?
6: ?000000000074fec4? - ?000000000074ffff?
7: ?00000000008dfdfc? - ?00000000008dffff?
8: ?000000000091fdec? - ?000000000091ffff?
9: ?000000000095fdf8? - ?000000000095ffff?
10: ?000000000099fed4? - ?000000000099ffff?
11: ?00000000009d95fc? - ?00000000009dffff?
12: ?0000000000a1fdf8? - ?0000000000a1ffff?
13: ?0000000000a7fdfc? - ?0000000000a7ffff?
14: ?0000000000abfed4? - ?0000000000abffff?
Total memory region size ?00000000`0001c259?

Issuing a dt command for a static variable with this declaration:

struct CmdLine {
int tConsoleApp;
int tNoKernelFs;
int tInstallService;
char * szServiceExePath;
int tRunAsReadOnly;
};
CmdLine cmdLine;

I get this output:

0:008> dt -v App!cmdLine
Got address 010c2068 for symbol
struct CmdLine, 5 elements, 0x14 bytes
+0x000 tConsoleApp : 0
+0x004 tNoKernelFs : 0
+0x008 tInstallService : 0
+0x00c szServiceExePath : (null)
+0x010 tRunAsReadOnly : 0

CDB found, that cmdLine is stored at 010c2068.
According to the region list, 010c2068 is *not* contained in the dump.

My question:
Why displays the debugger values for the components of cmdLine?

You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com