Kernel Debugger Extension

WINDBG
1

I am trying to compile the wdjext sample with our kernel space header
files for use in debugging the dump files generated by our driver. There
is an issue since these header files are designed for kernel space and the
debugger extension is designed for user space there is conflicts between
ntdef.h and windef.h.

Is my approach incorrect? Should I not be compiling the header files in
with the debugger extension? The point is to be able to build the
debugger extension to work with modifications to our data structures over
time, so that it can be a part of the build environment.

Thanks

2

If I understand correctly you are including a .h file in both the
extension and the driver so they can share structure definations.

A better approach for this is to use the symbol type information to get
the structure information. While not as convienent as using a C stuct,
it does offer you the power to support multiple versions of your driver
with a single extension binary. It also allows that extension to work
on 32-bit and 64-bit versions of the drive.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Brion Philbin
Sent: Wednesday, October 15, 2003 8:02 AM
To: Kernel Debugging Interest List
Subject: [windbg] Kernel Debugger Extension

I am trying to compile the wdjext sample with our kernel space header
files for use in debugging the dump files generated by our driver.
There is an issue since these header files are designed for kernel space
and the debugger extension is designed for user space there is conflicts
between ntdef.h and windef.h.

Is my approach incorrect? Should I not be compiling the header files in
with the debugger extension? The point is to be able to build the
debugger extension to work with modifications to our data structures
over time, so that it can be a part of the build environment.

Thanks

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

3

Is there an API for getting the necessary information from the symbol
files? I cant find any documentation.

Thanks,
Brion

4

As far as I know there is no real documentation on writing extensions at
all.

I suggest getting the latest debugger at
http://www.microsoft.com/ddk/debugging. Do a custom install and select
the SDK and samples.

Looking at the samples and the SDK .h files should give you enough to go
on. Symbol information is available for both new & old style
extensions.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Brion Philbin
Sent: Wednesday, October 15, 2003 11:44 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Kernel Debugger Extension

Is there an API for getting the necessary information from the symbol
files? I cant find any documentation.

Thanks,
Brion

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