Debug build environment producing no symbols - why?

I am using MSVC 6.0, the latest SDK, and the Windows NT 4.0 DDK. I have two
systems, one an NT 4.0 (thrash) machine, and one a Win2K (dev) box. I have
the NT4.0 symbols installed on the nice box, and the debug version of NT4
WKSTA on the thrash machine, but system symbols are not the issue here …

I noticed a while back (after reinstalling my dev environment on the nice
machine) that my CHECKED driver builds were producing code that WINDBG did
not recognize. I ran DUMPBIN /HEADERS <mydriver.sys> and got a header that
said the symbols had been stripped. I also had no PDB or DBG files.
Mystery:I had previously been able to build symbols with this setup (this
being a few weeks ago, before I reinstalled my compiler and part of my
environment). The BUILD.LOG showed something was passing the compiler
(among other things) : ‘/Zi /Od /Oi /NDEBUG’, and the linker was using
/PDB:NONE. Now, some of those compiler flags look OK, but the /NDEBUG is
definitely wrong. After much labor, I traced it into the DEF file (the
SETENV files seem to be OK, and the environment shows nothing obviously
wrong [DBG=1 etc.]). Somewhere in there NDEBUG is getting set on. I
hardcoded it to _DEBUG. Still no symbols: /PDB:NONE is still on for the
linker. There must be some global setting that is thrashing all this, but
I’m d-mned if I can find it. This seems to be related to the compiler /
tools reinstall (which generated some glitches in the SETENV.BATs that I
have patched by hand).

Anyone know what is going on ???

Thanks gobs

Eric


You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com</mydriver.sys>

for the nt4 ddk, try adding the following 2 lines to your sources file:

- the following are used to generate windbg debug symbols

USE_PDB=1
LINKER_DBG_TYPE=-debugtype:both

sean

xxxxx@pacbell.net wrote:

I am using MSVC 6.0, the latest SDK, and the Windows NT 4.0 DDK. I have two
systems, one an NT 4.0 (thrash) machine, and one a Win2K (dev) box. I have
the NT4.0 symbols installed on the nice box, and the debug version of NT4
WKSTA on the thrash machine, but system symbols are not the issue here …

I noticed a while back (after reinstalling my dev environment on the nice
machine) that my CHECKED driver builds were producing code that WINDBG did
not recognize. I ran DUMPBIN /HEADERS <mydriver.sys> and got a header that
>said the symbols had been stripped. I also had no PDB or DBG files.
>Mystery:I had previously been able to build symbols with this setup (this
>being a few weeks ago, before I reinstalled my compiler and part of my
>environment). The BUILD.LOG showed something was passing the compiler
>(among other things) : ‘/Zi /Od /Oi /NDEBUG’, and the linker was using
>/PDB:NONE. Now, some of those compiler flags look OK, but the /NDEBUG is
>definitely wrong. After much labor, I traced it into the DEF file (the
>SETENV files seem to be OK, and the environment shows nothing obviously
>wrong [DBG=1 etc.]). Somewhere in there NDEBUG is getting set on. I
>hardcoded it to _DEBUG. Still no symbols: /PDB:NONE is still on for the
>linker. There must be some global setting that is thrashing all this, but
>I’m d-mned if I can find it. This seems to be related to the compiler /
>tools reinstall (which generated some glitches in the SETENV.BATs that I
>have patched by hand).
>
>Anyone know what is going on ???
>
>Thanks gobs
>
>Eric
>
>—
>You are currently subscribed to windbg as: xxxxx@stg.com
>To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>


You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com</mydriver.sys>