winddk3790 + debug

OSR_Community_User · January 22, 2006, 7:53am

Hello there,
i have recently installed the WINDDK\3790 and i have some problems and
some questions.

Questions:

Where are \libchk and \libfre ? I mean that after installation the
DDK directory has only one subdirectory named \lib.
Should i install an older DDK before this one?

Problems:
I cannot force the compiler to include debug information inside the
image. The pdb that is made is too small and is obvious that
there is something wrong with the debug information.
When i try to use nmsym it fails reporting that no debug information are
included in the image file.

i include my source file. Thanks.

TARGETNAME=atm4plus
TARGETTYPE=DRIVER
TARGETPATH=obj
DRIVERTYPE=WDM

TARGETLIBS=\
$(DDK_LIB_PATH)\int64.lib \
$(DDK_LIB_PATH)\wdm.lib \
$(DDK_LIB_PATH)\hal.lib \
$(DDK_LIB_PATH)\ntoskrnl.lib

C_DEFINES= /DONLYONCE=extern\
/Dnologo\
/DUNICODE\
/D_UNICODE

DEBUG=1
NTDEBUGTYPE=both
USE_PDB=0

MSC_WARNING_LEVEL=/WX /W3
I386_WARNING_LEVEL=/WX /W3
MSC_OPTIMIZATION=/Od

BROWSER_INFO=1
BSCMAKE_FLAGS=$(BSCMAKE_FLAGS) -n

LINKER_FLAGS= -base:“0x10000” -map -entry:“DriverEntry” -debug:full

SOURCES=\
atm4plus.cpp\
mydbgprint.cpp\
unicode.cpp\
eventlog.cpp\
dispatchPNPhandling.cpp\
dispatchio.cpp\
isrhandling.cpp\
memoryaccessfunctions.cpp\
channelhandling.cpp\
isrhandling.cpp

INCLUDES=\
c:\includes; \
$(DDKPATH)\inc\ddk\w2k; \
$(DDKPATH)\inc; \
$(MSTOOLS)\include;

David_J_Craig · January 22, 2006, 1:32pm

Where did you get all the lines you are using in this sources file? It
contains obsolete commands such as USE_PDB which should not be used.

“Nikolas Stylianides” wrote in message news:xxxxx@ntdev…
> Hello there,
> i have recently installed the WINDDK\3790 and i have some problems and
> some questions.
>
> Questions:
> 1. Where are \libchk and \libfre ? I mean that after installation the DDK
> directory has only one subdirectory named \lib.
> 2. Should i install an older DDK before this one?
>
> Problems:
> I cannot force the compiler to include debug information inside the image.
> The pdb that is made is too small and is obvious that
> there is something wrong with the debug information.
> When i try to use nmsym it fails reporting that no debug information are
> included in the image file.
>
> i include my source file. Thanks.
>
> TARGETNAME=atm4plus
> TARGETTYPE=DRIVER
> TARGETPATH=obj
> DRIVERTYPE=WDM
>
> TARGETLIBS= > $(DDK_LIB_PATH)\int64.lib > $(DDK_LIB_PATH)\wdm.lib > $(DDK_LIB_PATH)\hal.lib > $(DDK_LIB_PATH)\ntoskrnl.lib
>
> C_DEFINES= /DONLYONCE=extern > /Dnologo > /DUNICODE > /D_UNICODE
>
> DEBUG=1
> NTDEBUGTYPE=both
> USE_PDB=0
>
> MSC_WARNING_LEVEL=/WX /W3
> I386_WARNING_LEVEL=/WX /W3
> MSC_OPTIMIZATION=/Od
>
> BROWSER_INFO=1
> BSCMAKE_FLAGS=$(BSCMAKE_FLAGS) -n
>
> LINKER_FLAGS= -base:“0x10000” -map -entry:“DriverEntry” -debug:full
>
> SOURCES= > atm4plus.cpp > mydbgprint.cpp > unicode.cpp > eventlog.cpp > dispatchPNPhandling.cpp > dispatchio.cpp > isrhandling.cpp > memoryaccessfunctions.cpp > channelhandling.cpp > isrhandling.cpp
>
> INCLUDES= > c:\includes; > $(DDKPATH)\inc\ddk\w2k; > $(DDKPATH)\inc; > $(MSTOOLS)\include;
>
>
>

Mark_Roddy · January 22, 2006, 1:46pm

Answers, comments, etc. inline.

=====================
Mark Roddy DDK MVP
Windows 2003/XP/2000 Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com

i have recently installed the WINDDK\3790 and i have some
problems and some questions.

You should be installing the 3790.1830 ddk not the 3790 ddk, unless of
course you are also installing the soon-to-be-obsolete IFS kit, which
requires the 3790 ddk.

Questions:

Where are \libchk and \libfre ? I mean that after
installation the DDK directory has only one subdirectory named \lib.

Yeah, good point. That organization disappeared with the XP release of the
ddk. I actually didn’t notice this until you pointed it out. Your sources
file shouldn’t notice either. It seems that the ddk only comes with one
version of .lib files - most of which are just dll entry point definitions
and shouldn’t be different checked vs release os. However some of them are
static libraries - so you are only going to link with production static
libs.

Should i install an older DDK before this one?

Heck no! Please don’t do that and for sure do not install a new ddk on top
of an old ddk distribution.

Problems:
I cannot force the compiler to include debug information
inside the image. The pdb that is made is too small and is
obvious that there is something wrong with the debug information.
When i try to use nmsym it fails reporting that no debug
information are included in the image file.

i include my source file. Thanks.

Your sources file is non standard. Don’t define DEBUG or NTDEBUGTYPE or
USE_PDB. The debug type (checked or free) is picked up from the environment
and should not be embedded in the sources file.

TARGETNAME=atm4plus
TARGETTYPE=DRIVER
TARGETPATH=obj
DRIVERTYPE=WDM

TARGETLIBS=\
$(DDK_LIB_PATH)\int64.lib \
$(DDK_LIB_PATH)\wdm.lib \
$(DDK_LIB_PATH)\hal.lib \
$(DDK_LIB_PATH)\ntoskrnl.lib

C_DEFINES= /DONLYONCE=extern\
/Dnologo\
/DUNICODE\
/D_UNICODE

DEBUG=1
NTDEBUGTYPE=both
USE_PDB=0

MSC_WARNING_LEVEL=/WX /W3
I386_WARNING_LEVEL=/WX /W3
MSC_OPTIMIZATION=/Od

BROWSER_INFO=1
BSCMAKE_FLAGS=$(BSCMAKE_FLAGS) -n

LINKER_FLAGS= -base:“0x10000” -map -entry:“DriverEntry” -debug:full

SOURCES=\
atm4plus.cpp\
mydbgprint.cpp\
unicode.cpp\
eventlog.cpp\
dispatchPNPhandling.cpp\
dispatchio.cpp\
isrhandling.cpp\
memoryaccessfunctions.cpp\
channelhandling.cpp\
isrhandling.cpp

INCLUDES=\
c:\includes; \
$(DDKPATH)\inc\ddk\w2k; \
$(DDKPATH)\inc; \
$(MSTOOLS)\include;

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

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

Maxim_S_Shatskih · January 22, 2006, 7:38pm

> TARGETNAME=atm4plus

TARGETTYPE=DRIVER
TARGETPATH=obj

This is fine.

DRIVERTYPE=WDM

Not sure it is needed, but let it be.

TARGETLIBS=\
$(DDK_LIB_PATH)\int64.lib \
$(DDK_LIB_PATH)\wdm.lib \
$(DDK_LIB_PATH)\hal.lib \
$(DDK_LIB_PATH)\ntoskrnl.lib

HAL and NTOSKRNL are automatically included in DRIVER project type.

C_DEFINES= /DONLYONCE=extern\
/Dnologo\
/DUNICODE\
/D_UNICODE

Do you really need the UNICODE macro in the kernel, provided that everything is
Unicode there anyway?

Also please don’t forget the old C_DEFINES, so, be like:

C_DEFINES=$(C_DEFINES) -DMY_MACRO_1 -DMY_MACRO_2

DEBUG=1
NTDEBUGTYPE=both
USE_PDB=0

Replace these ones with USE_PDB=1

MSC_WARNING_LEVEL=/WX /W3

/W4 /WX is better.

MSC_OPTIMIZATION=/Od

Replace this with:

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

LINKER_FLAGS= -base:“0x10000” -map -entry:“DriverEntry” -debug:full

No need in this.

INCLUDES=\

Usually it is:

INCLUDES=$(BASEDIR)\inc;$(BASEDIR)\src\storage\inc

or such. The root of DDK install is BASEDIR IIRC.

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

Maxim_S_Shatskih · January 22, 2006, 7:51pm

> Your sources file is non standard. Don’t define DEBUG or NTDEBUGTYPE or

USE_PDB. The debug type (checked or free) is picked up from the

Why? I always use PDB for everything.

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

Mark_Roddy · January 23, 2006, 8:43am

It’s the default - you get pdb for everything.

=====================
Mark Roddy DDK MVP
Windows 2003/XP/2000 Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim
S. Shatskih
Sent: Sunday, January 22, 2006 7:54 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] winddk3790 + debug

> Your sources file is non standard. Don’t define DEBUG or
NTDEBUGTYPE
> or USE_PDB. The debug type (checked or free) is picked up from the

Why? I always use PDB for everything.

Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.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@hollistech.com To unsubscribe send a blank email to
xxxxx@lists.osr.com

OSR_Community_User · January 23, 2006, 8:46am

Thank you. I have removed the obsolete parameters.

I understand that the new version of debug files (written in documents)
is to exclude the symbols from the images and
just keep a reference of the pdb file. That is why my release version
and debug version is almost the same size.
But still, the pdb file of the checked build is too small. It is about
half the size of what i expected.

I am using softice for debugging. I try to load symbols but i fail.

P.S.
My code compiles just fine. The image is working too.

P.S. 2
Where can i find the version of my DDK. I have install it from the DVD
Disk 2426.6 April 2004.

Thanks.

OSR_Community_User · January 23, 2006, 5:55pm

What it seems very strange to me is that the image file and pdb file in
checked build and free build do
not differ much.

Checked build:
sys = 52K
pdb=139K

Free build:
sys = 49K
pdb=139K

It seems to me that the checked build does not include the full debug
information (code, symbols etc)
How can i make this happen? I really need to produce an NMS file for
softice debugging.

Thanks

OSR_Community_User · January 23, 2006, 7:10pm

Those numbers look right to me. The pdb files should be the slightly
larger in the free build and the .sys files should be slightly smaller.
You should be able to do full symbolic debugging with the pdb and sys
files of either free or checked builds.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Nikolas
Stylianides
Sent: Tuesday, January 24, 2006 4:45 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] winddk3790 + debug

What it seems very strange to me is that the image file and pdb file in
checked build and free build do
not differ much.

Checked build:
sys = 52K
pdb=139K

Free build:
sys = 49K
pdb=139K

It seems to me that the checked build does not include the full debug
information (code, symbols etc)
How can i make this happen? I really need to produce an NMS file for
softice debugging.

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@stratus.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

David_J_Craig · January 23, 2006, 7:33pm

If you use the correct softice utility it handles the program database file
just fine or somewhat OK, maybe.

“Nikolas Stylianides” wrote in message news:xxxxx@ntdev…
> What it seems very strange to me is that the image file and pdb file in
> checked build and free build do
> not differ much.
>
> Checked build:
> sys = 52K
> pdb=139K
>
> Free build:
> sys = 49K
> pdb=139K
>
> It seems to me that the checked build does not include the full debug
> information (code, symbols etc)
> How can i make this happen? I really need to produce an NMS file for
> softice debugging.
>
> Thanks
>
>

OSR_Community_User · January 24, 2006, 4:11am

David J. Craig wrote:

If you use the correct softice utility it handles the program database file
just fine or somewhat OK, maybe.

“Nikolas Stylianides” wrote in message news:xxxxx@ntdev…
>
>
>>What it seems very strange to me is that the image file and pdb file in
>>checked build and free build do
>>not differ much.
>>
>>Checked build:
>>sys = 52K
>>pdb=139K
>>
>>Free build:
>>sys = 49K
>>pdb=139K
>>
>>It seems to me that the checked build does not include the full debug
>>information (code, symbols etc)
>>How can i make this happen? I really need to produce an NMS file for
>>softice debugging.
>>
>>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@4plus.com
>To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
My softice version is 4.05.

i run the command “nmsym /load /trans my_driver.sys>NUL” and i get
“Error translating: No debug information found”

Is it possible to translate the pdb and sys into an nms ? Do i have to
forget softice from now on ?

David_J_Craig · January 24, 2006, 12:34pm

Call Numega tech support. With the high price of SoftIce support in
included. It does work, but I can’t think of any reason to use SoftIce
since windbg is far more reliable and free.

“Nikolas Stylianides” wrote in message news:xxxxx@ntdev…
> David J. Craig wrote:
>
>>If you use the correct softice utility it handles the program database
>>file just fine or somewhat OK, maybe.
>>
>>“Nikolas Stylianides” wrote in message
>>news:xxxxx@ntdev…
>>
>>>What it seems very strange to me is that the image file and pdb file in
>>>checked build and free build do
>>>not differ much.
>>>
>>>Checked build:
>>>sys = 52K
>>>pdb=139K
>>>
>>>Free build:
>>>sys = 49K
>>>pdb=139K
>>>
>>>It seems to me that the checked build does not include the full debug
>>>information (code, symbols etc)
>>>How can i make this happen? I really need to produce an NMS file for
>>>softice debugging.
>>>
>>>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@4plus.com
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>>
>>
> My softice version is 4.05.
>
> i run the command “nmsym /load /trans my_driver.sys>NUL” and i get “Error
> translating: No debug information found”
>
> Is it possible to translate the pdb and sys into an nms ? Do i have to
> forget softice from now on ?
>
>
>

OSR_Community_User · January 25, 2006, 8:14am

David J. Craig wrote:

Call Numega tech support. With the high price of SoftIce support in
included. It does work, but I can’t think of any reason to use SoftIce
since windbg is far more reliable and free.

“Nikolas Stylianides” wrote in message news:xxxxx@ntdev…
>
>
>>David J. Craig wrote:
>>
>>
>>
>>>If you use the correct softice utility it handles the program database
>>>file just fine or somewhat OK, maybe.
>>>
>>>“Nikolas Stylianides” wrote in message
>>>news:xxxxx@ntdev…
>>>
>>>
>>>
>>>>What it seems very strange to me is that the image file and pdb file in
>>>>checked build and free build do
>>>>not differ much.
>>>>
>>>>Checked build:
>>>>sys = 52K
>>>>pdb=139K
>>>>
>>>>Free build:
>>>>sys = 49K
>>>>pdb=139K
>>>>
>>>>It seems to me that the checked build does not include the full debug
>>>>information (code, symbols etc)
>>>>How can i make this happen? I really need to produce an NMS file for
>>>>softice debugging.
>>>>
>>>>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@4plus.com
>>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>>>
>>>
>>>
>>>
>>>
>>My softice version is 4.05.
>>
>>i run the command “nmsym /load /trans my_driver.sys>NUL” and i get “Error
>>translating: No debug information found”
>>
>>Is it possible to translate the pdb and sys into an nms ? Do i have to
>>forget softice from now on ?
>>
>>
>>
>>
>>
>
>
>
>—
>Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
>You are currently subscribed to ntdev as: xxxxx@4plus.com
>To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
I have a project that produces a sys file of size 50K and a pdb file of
size 139K.
I am using winddk\3790.

I have already red the documentation of the new debug format that MS is
supporting (Evrything inside the pdb).
Does this seems OK to anybody? I think that the pdb file is not normal.
The sys is functioning perfect. I cannot load
symbols and code in softice.

Can anybody give me a clear answer?

Thank you.

OSR_Community_User · January 25, 2006, 9:06am

Load the symbols from windbg and get back to us. There is nothing
obviously wrong with the sizes that you are reporting, I don’t know why
you are obsessed with these numbers. The standard build environment
produces a fully debuggable image. If windbg can debug the driver and
softice can’t, you have a problem with softice and you need to either
resolve the softice problem (see the suggestion to contact Compuware) or
switch to windbg.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Nikolas
Stylianides
Sent: Wednesday, January 25, 2006 8:15 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] winddk3790 + debug

David J. Craig wrote:

Call Numega tech support. With the high price of SoftIce support in
included. It does work, but I can’t think of any reason to use SoftIce

since windbg is far more reliable and free.

“Nikolas Stylianides” wrote in message
news:xxxxx@ntdev…
>
>
>>David J. Craig wrote:
>>
>>
>>
>>>If you use the correct softice utility it handles the program
database
>>>file just fine or somewhat OK, maybe.
>>>
>>>“Nikolas Stylianides” wrote in message
>>>news:xxxxx@ntdev…
>>>
>>>
>>>
>>>>What it seems very strange to me is that the image file and pdb file
in
>>>>checked build and free build do
>>>>not differ much.
>>>>
>>>>Checked build:
>>>>sys = 52K
>>>>pdb=139K
>>>>
>>>>Free build:
>>>>sys = 49K
>>>>pdb=139K
>>>>
>>>>It seems to me that the checked build does not include the full
debug
>>>>information (code, symbols etc)
>>>>How can i make this happen? I really need to produce an NMS file
for
>>>>softice debugging.
>>>>
>>>>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@4plus.com
>>>To unsubscribe send a blank email to
xxxxx@lists.osr.com
>>>
>>>
>>>
>>>
>>>
>>My softice version is 4.05.
>>
>>i run the command “nmsym /load /trans my_driver.sys>NUL” and i get
“Error
>>translating: No debug information found”
>>
>>Is it possible to translate the pdb and sys into an nms ? Do i have to

>>forget softice from now on ?
>>
>>
>>
>>
>>
>
>
>
>—
>Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
>You are currently subscribed to ntdev as: xxxxx@4plus.com
>To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
I have a project that produces a sys file of size 50K and a pdb file of
size 139K.
I am using winddk\3790.

I have already red the documentation of the new debug format that MS is
supporting (Evrything inside the pdb).
Does this seems OK to anybody? I think that the pdb file is not normal.
The sys is functioning perfect. I cannot load
symbols and code in softice.

Can anybody give me a clear answer?

Thank you.

—
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

Michal_Vodicka-2 · January 25, 2006, 6:11pm

> ----------

From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Nikolas Stylianides[SMTP:xxxxx@4plus.com]
Reply To: Windows System Software Devs Interest List
Sent: Wednesday, January 25, 2006 2:14 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] winddk3790 + debug

I have already red the documentation of the new debug format that MS is
supporting (Evrything inside the pdb).
Does this seems OK to anybody? I think that the pdb file is not normal.
The sys is functioning perfect. I cannot load
symbols and code in softice.

SoftICE 4.05 is rather old and it is quite possible it doesn’t support new PDB format introduced in VC 7.0. DDK compiler you’re using already generates new symbols format. PDB starts with following text: “Microsoft C/C++ MSF 7.00” whereas previous version had this one: “Microsoft C/C++ program database 2.00”. There are some undocumented parameters which allow to force compiler to generate old symbols format. Search archives or use Google if you want to try it.

BTW, I have no problem with SoftICE from Driver Studio 3.2.

Can anybody give me a clear answer?

You already got it. Call Compuware tech support.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

Maxim_S_Shatskih · January 25, 2006, 11:32pm

>whereas previous version had this one: "Microsoft C/C++ program database

2.00". There are some undocumented parameters which allow to force to
generate old symbols format.

Really? The 2003 SP1 DDK (contrary to 2003 DDK) is the point-in-time where the
PDB format changed, and sorry, no more debugging with MSVC 6 in user mode.

So, if I will be able to force the 2003 SP1 DDK (latest pre-WDK) to generate
old PDBs, I will still be able to retain this small lovely debugger, which is
very usable for simple tasks (though not as powerful as WinDbg).

Yes, I use DDK to build user-mode stuff, lots of it. After all, if MS uses this
build env (or something like it) to build the whole OS, then why not me?

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

Michal_Vodicka-2 · January 25, 2006, 11:59pm

> ----------

From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Maxim S. Shatskih[SMTP:xxxxx@storagecraft.com]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, January 26, 2006 5:35 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] winddk3790 + debug

>whereas previous version had this one: “Microsoft C/C++ program database
>2.00”. There are some undocumented parameters which allow to force to
>generate old symbols format.

Really? The 2003 SP1 DDK (contrary to 2003 DDK) is the point-in-time where the
PDB format changed, and sorry, no more debugging with MSVC 6 in user mode.

So, if I will be able to force the 2003 SP1 DDK (latest pre-WDK) to generate
old PDBs, I will still be able to retain this small lovely debugger, which is
very usable for simple tasks (though not as powerful as WinDbg).

OK, I examined my old VxD makefiles and there is -debugtype:vc6 linker option used. I needed it because used DDK compiler but the latest SoftICE version for w9x doesn’t support new symbols format. You can also try /Zvc6 cl option which is also somewhat related with old symbols.

I don’t remember how exactly to specify it in SOURCES but I’m sure there is a way and you’ll be able to find it.

Yes, I use DDK to build user-mode stuff, lots of it. After all, if MS uses this
build env (or something like it) to build the whole OS, then why not me?

Me too However, for what do you need a debugger? Good traces are much better and I use debugger mostly as assert and bugcheck catcher only. Debuggers are quite useless for real time problems and when problem occurs at customer’s machine on the other side of the world.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

Maxim_S_Shatskih · January 26, 2006, 4:07am

>Me too However, for what do you need a debugger? Good traces are much

better and I use debugger mostly as assert and bugcheck catcher only.

To look into traces, starting from the moment where something is going wrong. I
put __asm{int 3} to the code there and rebuild, then look in the debugger.

Examining the memory layouts and structure contents at such points can be a
good idea too, single-stepping is lesser (this is more for beginners IMHO), but
useful anyway.

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

Michal_Vodicka-2 · January 26, 2006, 3:19pm

> ----------

From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Maxim S. Shatskih[SMTP:xxxxx@storagecraft.com]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, January 26, 2006 10:10 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] winddk3790 + debug

To look into traces, starting from the moment where something is going wrong. I
put __asm{int 3} to the code there and rebuild, then look in the debugger.

Too much work I just set color filter in DbgView. In most cases, problems are reproduced by other people who just send logs to me. The best thing on the traces is that the most annoying work with reproducing problem can be made by somebody else

Examining the memory layouts and structure contents at such points can be a
good idea too,

Yes, sometimes. In such cases I let QA people to make crashdump or, if I have to examine problem locally, set breakpoint on text in SoftICE (filter command, very useful). No rebuild needed

single-stepping is lesser (this is more for beginners IMHO), but
useful anyway.

I’d agree mainly with beginners part. I don’t remember when single stepped my own code last time. It can be useful when OS code has to be examined.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]