Producing debug information for XP DDK

NTDEV
1

[Apologies if this appears twice. The first attempt seems to have
fallen into a black hole.]

I’m moving my driver development onto XP. (yeah, things move kinda slow
this close to the South :slight_smile: ) WinDbg 6 is running smoothly (and even
using the symbol server!), but it wants .pdb or .dbg symbol files. Most
of my drivers are built on Walter Oney’s WDM framework and I can’t seem
to convince VS6.0 to produce a .pdb file. Have I missed something
trivial, or will I need to move the code into the DDK build environment?
And if I have to move, are there any gotchas? Or is it pretty much
just moving source files into the build tree? Presumptive thanks.

2

Move to the DDK build environment. If you still want to develop in the IDE
then get ddkbuild.bat from either www.osronline.com or www.hollistech.com.

–
Mark Cariddi
Consulting Associate
OSR, Open Systems Resources, Inc.
http://www.osr.com/
“Roy Silvernail” wrote in message
news:xxxxx@ntdev…
> [Apologies if this appears twice. The first attempt seems to have
> fallen into a black hole.]
>
> I’m moving my driver development onto XP. (yeah, things move kinda slow
> this close to the South :slight_smile: ) WinDbg 6 is running smoothly (and even
> using the symbol server!), but it wants .pdb or .dbg symbol files. Most
> of my drivers are built on Walter Oney’s WDM framework and I can’t seem
> to convince VS6.0 to produce a .pdb file. Have I missed something
> trivial, or will I need to move the code into the DDK build environment?
> And if I have to move, are there any gotchas? Or is it pretty much
> just moving source files into the build tree? Presumptive thanks.
>

3

Not familiar with the W.O. WDM Framework, but if it has a “Debug build” or
“Checked build” option, it should produce a .PDB file.

Or, if you can modify the compile options, you should set:
/Zi

Turning off optimisation is probably also a good idea, as the optimisation
in default release build is pretty much non-source debugging, because the
compiler generates code that is not easy for the debugger to follow. It
seems like the debugger can’t understand register variables unless the same
register is used for the same purpose throughout a function, so if a
variable has been loaded into a register, then some other value is in the
register later on, you don’t get much sense out of the debuggers “local
variable” view, for example.

If there’s no other way to set the optimisation level, you can add /Od to
the end of the command line for the compiler, which will give a warning when
it overrides the optimisation level, but will turn off optimisation.

Hope this helps.

–
Mats

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Roy Silvernail
Sent: Friday, July 16, 2004 1:14 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Producing debug information for XP DDK

[Apologies if this appears twice. The first attempt seems to have
fallen into a black hole.]

I’m moving my driver development onto XP. (yeah, things move
kinda slow
this close to the South :slight_smile: ) WinDbg 6 is running smoothly (and even
using the symbol server!), but it wants .pdb or .dbg symbol
files. Most
of my drivers are built on Walter Oney’s WDM framework and I
can’t seem
to convince VS6.0 to produce a .pdb file. Have I missed something
trivial, or will I need to move the code into the DDK build
environment?
And if I have to move, are there any gotchas? Or is it pretty much
just moving source files into the build tree? Presumptive thanks.

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

Is Project Settings C/C++ Debug Info set to Program Database or C7 compatible
?

Regards,
PaoloC

– Messaggio originale –
Date: Fri, 16 Jul 2004 08:13:54 -0400
From: Roy Silvernail
>Subject: [ntdev] Producing debug information for XP DDK
>To: “Windows System Software Devs Interest List”
>Reply-To: “Windows System Software Devs Interest List”
>
>
>[Apologies if this appears twice. The first attempt seems to have
>fallen into a black hole.]
>
>I’m moving my driver development onto XP. (yeah, things move kinda slow

>this close to the South :slight_smile: ) WinDbg 6 is running smoothly (and even
>using the symbol server!), but it wants .pdb or .dbg symbol files. Most
>
>of my drivers are built on Walter Oney’s WDM framework and I can’t seem

>to convince VS6.0 to produce a .pdb file. Have I missed something
>trivial, or will I need to move the code into the DDK build environment?
>
> And if I have to move, are there any gotchas? Or is it pretty much
>just moving source files into the build tree? Presumptive thanks.
>
>—
>Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
>You are currently subscribed to ntdev as: xxxxx@tin.it
>To unsubscribe send a blank email to xxxxx@lists.osr.com

5

AFAIK if you set a USE_PDB=1 environment variable, you will get a .pdb file.

Alberto.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Roy Silvernail
Sent: Friday, July 16, 2004 8:14 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Producing debug information for XP DDK

[Apologies if this appears twice. The first attempt seems to have
fallen into a black hole.]

I’m moving my driver development onto XP. (yeah, things move kinda slow
this close to the South :slight_smile: ) WinDbg 6 is running smoothly (and even
using the symbol server!), but it wants .pdb or .dbg symbol files. Most
of my drivers are built on Walter Oney’s WDM framework and I can’t seem
to convince VS6.0 to produce a .pdb file. Have I missed something
trivial, or will I need to move the code into the DDK build environment?
And if I have to move, are there any gotchas? Or is it pretty much
just moving source files into the build tree? Presumptive thanks.

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

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

The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.

6

AFAIK if you set the environment variable USE_PDB=1 you get a pdb.

Alberto.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of
xxxxx@3Dlabs.com
Sent: Friday, July 16, 2004 8:36 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Producing debug information for XP DDK

Not familiar with the W.O. WDM Framework, but if it has a “Debug build” or
“Checked build” option, it should produce a .PDB file.

Or, if you can modify the compile options, you should set:
/Zi

Turning off optimisation is probably also a good idea, as the optimisation
in default release build is pretty much non-source debugging, because the
compiler generates code that is not easy for the debugger to follow. It
seems like the debugger can’t understand register variables unless the same
register is used for the same purpose throughout a function, so if a
variable has been loaded into a register, then some other value is in the
register later on, you don’t get much sense out of the debuggers “local
variable” view, for example.

If there’s no other way to set the optimisation level, you can add /Od to
the end of the command line for the compiler, which will give a warning when
it overrides the optimisation level, but will turn off optimisation.

Hope this helps.

–
Mats

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Roy Silvernail
Sent: Friday, July 16, 2004 1:14 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Producing debug information for XP DDK

[Apologies if this appears twice. The first attempt seems to have
fallen into a black hole.]

I’m moving my driver development onto XP. (yeah, things move
kinda slow
this close to the South :slight_smile: ) WinDbg 6 is running smoothly (and even
using the symbol server!), but it wants .pdb or .dbg symbol
files. Most
of my drivers are built on Walter Oney’s WDM framework and I
can’t seem
to convince VS6.0 to produce a .pdb file. Have I missed something
trivial, or will I need to move the code into the DDK build
environment?
And if I have to move, are there any gotchas? Or is it pretty much
just moving source files into the build tree? Presumptive thanks.

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

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

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

The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.

7

The IDE is very comfortable and there should be no issues that are
insurmountable enough to force anyone to go back to the dos box. You can
also use our Src2Dsp utility, it’s a free download from
http://frontline.compuware.com/nashua/patches/utility.htm. It converts your
dirs or sources file into a VC6 workspace/project or into a VS.NET solution,
and it can also convert your VC6 .dsp into a VS.NET .sln. This is the 3.1
version, in a few weeks time we’ll post the 3.2 version that also generates
.sln files for .NET 2005.

Alberto.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Mark Cariddi
Sent: Friday, July 16, 2004 8:19 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Producing debug information for XP DDK

Move to the DDK build environment. If you still want to develop in the IDE
then get ddkbuild.bat from either www.osronline.com or www.hollistech.com.

–
Mark Cariddi
Consulting Associate
OSR, Open Systems Resources, Inc.
http://www.osr.com/
“Roy Silvernail” wrote in message
news:xxxxx@ntdev…
> [Apologies if this appears twice. The first attempt seems to have
> fallen into a black hole.]
>
> I’m moving my driver development onto XP. (yeah, things move kinda slow
> this close to the South :slight_smile: ) WinDbg 6 is running smoothly (and even
> using the symbol server!), but it wants .pdb or .dbg symbol files. Most
> of my drivers are built on Walter Oney’s WDM framework and I can’t seem
> to convince VS6.0 to produce a .pdb file. Have I missed something
> trivial, or will I need to move the code into the DDK build environment?
> And if I have to move, are there any gotchas? Or is it pretty much
> just moving source files into the build tree? Presumptive thanks.
>

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

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

The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.

8

The challenge here is that you still are not using the right compiler, and
that Microsoft does change the compile switches every so often. Using
anything but the DDK environment is one of the greatest acts of stupidity
one can do! In fact I know of a firm that dictated the DDK environment, and
found out the driver they got was built otherwise, they are contemplating
suing the supplier for not meeting the reuqirements since there were several
bugs found by moving to correct environment.

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Moreira, Alberto” wrote in message
news:xxxxx@ntdev…
> The IDE is very comfortable and there should be no issues that are
> insurmountable enough to force anyone to go back to the dos box. You can
> also use our Src2Dsp utility, it’s a free download from
> http://frontline.compuware.com/nashua/patches/utility.htm. It converts
your
> dirs or sources file into a VC6 workspace/project or into a VS.NET
solution,
> and it can also convert your VC6 .dsp into a VS.NET .sln. This is the 3.1
> version, in a few weeks time we’ll post the 3.2 version that also
generates
> .sln files for .NET 2005.
>
> Alberto.
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Mark Cariddi
> Sent: Friday, July 16, 2004 8:19 AM
> To: Windows System Software Devs Interest List
> Subject: Re:[ntdev] Producing debug information for XP DDK
>
>
> Move to the DDK build environment. If you still want to develop in the
IDE
> then get ddkbuild.bat from either www.osronline.com or www.hollistech.com.
>
>
>
> –
> Mark Cariddi
> Consulting Associate
> OSR, Open Systems Resources, Inc.
> http://www.osr.com/
> “Roy Silvernail” wrote in message
> news:xxxxx@ntdev…
> > [Apologies if this appears twice. The first attempt seems to have
> > fallen into a black hole.]
> >
> > I’m moving my driver development onto XP. (yeah, things move kinda slow
> > this close to the South :slight_smile: ) WinDbg 6 is running smoothly (and even
> > using the symbol server!), but it wants .pdb or .dbg symbol files. Most
> > of my drivers are built on Walter Oney’s WDM framework and I can’t seem
> > to convince VS6.0 to produce a .pdb file. Have I missed something
> > trivial, or will I need to move the code into the DDK build environment?
> > And if I have to move, are there any gotchas? Or is it pretty much
> > just moving source files into the build tree? Presumptive thanks.
> >
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@compuware.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
> The contents of this e-mail are intended for the named addressee only. It
> contains information that may be confidential. Unless you are the named
> addressee or an authorized designee, you may not copy or use it, or
disclose
> it to anyone else. If you received it in error please notify us
immediately
> and then destroy it.
>
>

9

Try this - (maybe a dirty way to do it!!!)

In your Visual Studio IDE, under -
Project -> Settings -> Link Tab -> Project Options …

Look for /pdb option, if not present you could add

/pdb:“YourPath\file.pdb”

-g

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Moreira, Alberto
Sent: Friday, July 16, 2004 7:43 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Producing debug information for XP DDK

The IDE is very comfortable and there should be no issues that are
insurmountable enough to force anyone to go back to the dos box. You can
also use our Src2Dsp utility, it’s a free download from
http://frontline.compuware.com/nashua/patches/utility.htm. It converts
your dirs or sources file into a VC6 workspace/project or into a VS.NET
solution, and it can also convert your VC6 .dsp into a VS.NET .sln. This
is the 3.1 version, in a few weeks time we’ll post the 3.2 version that
also generates .sln files for .NET 2005.

Alberto.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Mark Cariddi
Sent: Friday, July 16, 2004 8:19 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Producing debug information for XP DDK

Move to the DDK build environment. If you still want to develop in the
IDE
then get ddkbuild.bat from either www.osronline.com or
www.hollistech.com.

–
Mark Cariddi
Consulting Associate
OSR, Open Systems Resources, Inc.
http://www.osr.com/
“Roy Silvernail” wrote in message
news:xxxxx@ntdev…
> [Apologies if this appears twice. The first attempt seems to have
> fallen into a black hole.]
>
> I’m moving my driver development onto XP. (yeah, things move kinda
> slow this close to the South :slight_smile: ) WinDbg 6 is running smoothly (and
> even using the symbol server!), but it wants .pdb or .dbg symbol
> files. Most of my drivers are built on Walter Oney’s WDM framework
> and I can’t seem to convince VS6.0 to produce a .pdb file. Have I
> missed something trivial, or will I need to move the code into the DDK
build environment?
> And if I have to move, are there any gotchas? Or is it pretty much
> just moving source files into the build tree? Presumptive thanks.
>

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

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

The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the
named addressee or an authorized designee, you may not copy or use it,
or disclose it to anyone else. If you received it in error please notify
us immediately and then destroy it.

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

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

10

The IDE is very comfortable and there should be no issues that are
insurmountable enough to force anyone to go back to the dos box: once you
get used to drive a Lexus, it’s hard to go back to that Honda Civic. You can
also use our Src2Dsp utility, it’s a free download from
http://frontline.compuware.com/nashua/patches/utility.htm. It converts your
dirs or sources file into a VC6 workspace/project or into a VS.NET solution,
and it can also convert your VC6 .dsp into a VS.NET .sln. This is the 3.1
version, in a few weeks time we’ll post the 3.2 version that also generates
.sln files for .NET 2005.

-----Original Message-----
On Behalf Of Mark Cariddi
Sent: Friday, July 16, 2004 8:19 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Producing debug information for XP DDK

Move to the DDK build environment. If you still want to develop in the IDE
then get ddkbuild.bat from either www.osronline.com or www.hollistech.com.

–
Mark Cariddi
Consulting Associate
OSR, Open Systems Resources, Inc.
http://www.osr.com/

The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.

11

You can tell the IDE to use whatever compiler you want by changing the
directory sequence at tools/options/directories, it’s a five-second job: the
IDE is not hard-linked to any specific compiler. Also, Microsoft only
changes DDK settings when a new DDK version comes up, and even then, the
likelihood that compiler switches break an existing build aren’t that great

  • and one touch to the sources file plus running something like src2dsp
    again will handle the problem. Furthermore, you don’t necessarily have to
    upgrade a driver’s build environment for every intermediate DDK release -
    for example, we use 2260, 3790 and 3790.1184, depending on what platform
    we’re addressing, and that’s it.

And maybe I’m getting spoiled, but if I want to use build.exe, I can click
on my “build button” on the IDE, there, done. But then, you need DriverWorks
for that, although the addin to the IDE is trivial to write.

Alberto.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Don Burn
Sent: Friday, July 16, 2004 10:25 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Producing debug information for XP DDK

The challenge here is that you still are not using the right compiler, and
that Microsoft does change the compile switches every so often. Using
anything but the DDK environment is one of the greatest acts of stupidity
one can do! In fact I know of a firm that dictated the DDK environment, and
found out the driver they got was built otherwise, they are contemplating
suing the supplier for not meeting the reuqirements since there were several
bugs found by moving to correct environment.

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Moreira, Alberto” wrote in message
news:xxxxx@ntdev…
> The IDE is very comfortable and there should be no issues that are
> insurmountable enough to force anyone to go back to the dos box. You can
> also use our Src2Dsp utility, it’s a free download from
> http://frontline.compuware.com/nashua/patches/utility.htm. It converts
your
> dirs or sources file into a VC6 workspace/project or into a VS.NET
solution,
> and it can also convert your VC6 .dsp into a VS.NET .sln. This is the 3.1
> version, in a few weeks time we’ll post the 3.2 version that also
generates
> .sln files for .NET 2005.
>
> Alberto.
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Mark Cariddi
> Sent: Friday, July 16, 2004 8:19 AM
> To: Windows System Software Devs Interest List
> Subject: Re:[ntdev] Producing debug information for XP DDK
>
>
> Move to the DDK build environment. If you still want to develop in the
IDE
> then get ddkbuild.bat from either www.osronline.com or www.hollistech.com.
>
>
>
> –
> Mark Cariddi
> Consulting Associate
> OSR, Open Systems Resources, Inc.
> http://www.osr.com/
> “Roy Silvernail” wrote in message
> news:xxxxx@ntdev…
> > [Apologies if this appears twice. The first attempt seems to have
> > fallen into a black hole.]
> >
> > I’m moving my driver development onto XP. (yeah, things move kinda slow
> > this close to the South :slight_smile: ) WinDbg 6 is running smoothly (and even
> > using the symbol server!), but it wants .pdb or .dbg symbol files. Most
> > of my drivers are built on Walter Oney’s WDM framework and I can’t seem
> > to convince VS6.0 to produce a .pdb file. Have I missed something
> > trivial, or will I need to move the code into the DDK build environment?
> > And if I have to move, are there any gotchas? Or is it pretty much
> > just moving source files into the build tree? Presumptive thanks.
> >
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@compuware.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
> The contents of this e-mail are intended for the named addressee only. It
> contains information that may be confidential. Unless you are the named
> addressee or an authorized designee, you may not copy or use it, or
disclose
> it to anyone else. If you received it in error please notify us
immediately
> and then destroy it.
>
>

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

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

The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.

12

Try project/settings/C++/DebugInfo and set it to “Program Database”.

Alberto.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Girish Kulkarni
(kulkis)
Sent: Friday, July 16, 2004 10:29 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Producing debug information for XP DDK

Try this - (maybe a dirty way to do it!!!)

In your Visual Studio IDE, under -
Project -> Settings -> Link Tab -> Project Options …

Look for /pdb option, if not present you could add

/pdb:“YourPath\file.pdb”

-g

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Moreira, Alberto
Sent: Friday, July 16, 2004 7:43 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Producing debug information for XP DDK

The IDE is very comfortable and there should be no issues that are
insurmountable enough to force anyone to go back to the dos box. You can
also use our Src2Dsp utility, it’s a free download from
http://frontline.compuware.com/nashua/patches/utility.htm. It converts
your dirs or sources file into a VC6 workspace/project or into a VS.NET
solution, and it can also convert your VC6 .dsp into a VS.NET .sln. This
is the 3.1 version, in a few weeks time we’ll post the 3.2 version that
also generates .sln files for .NET 2005.

Alberto.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Mark Cariddi
Sent: Friday, July 16, 2004 8:19 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Producing debug information for XP DDK

Move to the DDK build environment. If you still want to develop in the
IDE
then get ddkbuild.bat from either www.osronline.com or
www.hollistech.com.

–
Mark Cariddi
Consulting Associate
OSR, Open Systems Resources, Inc.
http://www.osr.com/
“Roy Silvernail” wrote in message
news:xxxxx@ntdev…
> [Apologies if this appears twice. The first attempt seems to have
> fallen into a black hole.]
>
> I’m moving my driver development onto XP. (yeah, things move kinda
> slow this close to the South :slight_smile: ) WinDbg 6 is running smoothly (and
> even using the symbol server!), but it wants .pdb or .dbg symbol
> files. Most of my drivers are built on Walter Oney’s WDM framework
> and I can’t seem to convince VS6.0 to produce a .pdb file. Have I
> missed something trivial, or will I need to move the code into the DDK
build environment?
> And if I have to move, are there any gotchas? Or is it pretty much
> just moving source files into the build tree? Presumptive thanks.
>

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

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

The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the
named addressee or an authorized designee, you may not copy or use it,
or disclose it to anyone else. If you received it in error please notify
us immediately and then destroy it.

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

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

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

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

The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.

13

Mark Cariddi wrote:

Move to the DDK build environment. If you still want to develop in the IDE
then get ddkbuild.bat from either www.osronline.com or www.hollistech.com.

I did, and it was pretty much painless. I just needed to create a
sources file. Of course, after I did this, the bug I was chasing (BSOD
presumed to be a multiple-CPU-related) no longer shows up. It’s either
more deeply seated than I thought, or it was an artifact of building on
VS6.0 that was fixed by moving to the DDK build environment. Either
way, I get to use it as an argument in favor of relegating more targets
to the legacy pile. (if my managers had their way, we’d still be doing
new development on NT and 98, along with 2K/XP)

BTW, an IDE isn’t that important to me for driver work. I actually use
CodeWright more often as my editor anyway.

Thanks for the tip.

14

That’s why using SOURCES file has its advantages :slight_smile:

As about VS6.0 - it always generated the PDB file for me.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

----- Original Message -----
From: “Roy Silvernail”
Newsgroups: ntdev
To: “Windows System Software Devs Interest List”
Sent: Friday, July 16, 2004 4:13 PM
Subject: [ntdev] Producing debug information for XP DDK

> [Apologies if this appears twice. The first attempt seems to have
> fallen into a black hole.]
>
> I’m moving my driver development onto XP. (yeah, things move kinda slow
> this close to the South :slight_smile: ) WinDbg 6 is running smoothly (and even
> using the symbol server!), but it wants .pdb or .dbg symbol files. Most
> of my drivers are built on Walter Oney’s WDM framework and I can’t seem
> to convince VS6.0 to produce a .pdb file. Have I missed something
> trivial, or will I need to move the code into the DDK build environment?
> And if I have to move, are there any gotchas? Or is it pretty much
> just moving source files into the build tree? Presumptive thanks.
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com

15

> If there’s no other way to set the optimisation level, you can add /Od to

the end of the command line for the compiler, which will give a warning when

In SOURCES file, add:

!IF !$(FREEBUILD)
MSC_OPTIMIZATION=/Od
!ENDIF

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

16

Girish Kulkarni (kulkis) wrote:

Try this - (maybe a dirty way to do it!!!)

In your Visual Studio IDE, under -
Project -> Settings -> Link Tab -> Project Options …

Look for /pdb option, if not present you could add

/pdb:“YourPath\file.pdb”

Strangely enough, the “Use program database” option was checked and the
/pdb option was present in the link options. But despite this, no .pdb
was created.

17

>>I did, and it was pretty much painless. I just needed to create a

>sources file. Of course, after I did this, the bug I was chasing
(BSOD
>presumed to be a multiple-CPU-related) no longer shows up.

By any chance, are you now building a debug version of your driver ? If
you have timing issues in your code, you may not hit it, with a debug
version of your driver.

-g

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Roy Silvernail
Sent: Friday, July 16, 2004 8:36 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Producing debug information for XP DDK

Mark Cariddi wrote:

Move to the DDK build environment. If you still want to develop in
the IDE
then get ddkbuild.bat from either www.osronline.com or
www.hollistech.com.

I did, and it was pretty much painless. I just needed to create a
sources file. Of course, after I did this, the bug I was chasing (BSOD
presumed to be a multiple-CPU-related) no longer shows up. It’s either
more deeply seated than I thought, or it was an artifact of building on
VS6.0 that was fixed by moving to the DDK build environment. Either
way, I get to use it as an argument in favor of relegating more targets
to the legacy pile. (if my managers had their way, we’d still be doing
new development on NT and 98, along with 2K/XP)

BTW, an IDE isn’t that important to me for driver work. I actually use
CodeWright more often as my editor anyway.

Thanks for the tip.

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

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