debug info in driver

NTDEV
1

Hi,
when using the checked build of the ddk environment, is it sufficient to
just set ntdebug and ntdebugtype environ variables to have complete debug
info in the driver.

are there any other flags, cmd line parameters to be used? also does the
source file contain any other information. after doing the debug build, my
.sys file seems to be very small though i have a separate pdb file. curious
if i m doing the rite thing.

kutty

2

You shouldn’t set anything in your environment, you should instead use the
standard checked build environment provided by the ddk. It is quite normal
for a checked driver to have a relatively small .sys file and a relatively
large .pdb file.

=====================
Mark Roddy

-----Original Message-----
From: Kutty Banerjee [mailto:xxxxx@wpi.edu]
Sent: Tuesday, July 06, 2004 11:18 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] debug info in driver

Hi,
when using the checked build of the ddk environment, is it sufficient to
just set ntdebug and ntdebugtype environ variables to have complete debug
info in the driver.

are there any other flags, cmd line parameters to be used? also does the
source file contain any other information. after doing the debug build, my
.sys file seems to be very small though i have a separate pdb file. curious
if i m doing the rite thing.

kutty

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

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

3

> -----Original Message-----

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Kutty Banerjee
Sent: Tuesday, July 06, 2004 4:18 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] debug info in driver

Hi,
when using the checked build of the ddk environment, is it
sufficient to
just set ntdebug and ntdebugtype environ variables to have
complete debug
info in the driver.

are there any other flags, cmd line parameters to be used?
also does the
source file contain any other information. after doing the
debug build, my
.sys file seems to be very small though i have a separate pdb
file. curious
if i m doing the rite thing.

The normal thing is that you get a separate .PDB for each .SYS (or .DLL)
that you produce. These .PDB files are placed in a place which can be
reached by the debugger (WinDBG for example). The .PDB contains all symbols,
source-line info, data structure definitions, etc that the debugger needs to
keep you informed about symbols, where in the source a particular assembly
instruction belongs, etc.

You’ll obviously need to set the debugger to know where your source files
are too, so that it can display that in the source view, otherwise you’ll
only be able to view data and generated assembler instructions, which isn’t
always what you’d want…

There’s only a little bit of debug information in the .SYS file (global
symbols would be there for instance), so I’d expect a debug and release
version to be fairly similar in size.

[Oh, and you can of course ask the build tool to generate a .PDB for release
build too, should you have a heizenbug at any time].

–
Mats

kutty

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@3dlabs.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

4

IIRC, you dont need to do anything special for building debug build. The pdb
file size should be vastly different for release and debug build, if I
recall. But in any case, since your postings are related to
symbols/debug/linking etc… I would recommend you to take a pick on the msj
archive, there are some great old articles about the whole business of PE,
compile, link, symbols. Also MS site has a very very good doc about PE
discussion…
Finally you should really look at John Robbins “Debugging application” book,
he is also a regular contributor of MSDN mag…

-pro

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Kutty Banerjee
Sent: Tuesday, July 06, 2004 8:18 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] debug info in driver

Hi,
when using the checked build of the ddk environment, is it sufficient to
just set ntdebug and ntdebugtype environ variables to have complete debug
info in the driver.

are there any other flags, cmd line parameters to be used? also does the
source file contain any other information. after doing the debug build, my
.sys file seems to be very small though i have a separate pdb file. curious
if i m doing the rite thing.

kutty

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

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