Hi,
From: Motonori Shindo <mshindo@xxxxxxxxxxx>
Subject: Re: [Ethereal-dev] Re: How do I get .pdb file under Win32
Date: Wed, 12 Dec 2001 10:51:16 +0900 (JST)
> I also tried to find a way to manipulate macros in nmake whether I can
> trim some string out of it keeping others intact, but there seems not
> in nmake. If nmake can do a command substitution (like back-quoting in
> UNIX shells), we may be able to use 'sed' to substitute /PDB:NONE to
> anything we want. I'll look into that.
I looked around the MS documents but was unable to find such a
mechanism in NMAKE unfortunately.
However, I also found the following description regarding /PDB:NONE
option:
The linker does not create a PDB, but instead puts old-style
debugging information into the .EXE file or DLL. The linker then
calls the CVPACK.EXE tool, which must be in the same directory as
LINK.EXE or in a directory in the PATH environment variable.
Given this description, do we really need to have separate *.pdb files
first of all? If debugging information is embedded into *.exe and we
can get all the information like a stack trace, then *.exe created
with /PDB:NONE option would suffice for distribution, woudln't it? The
same thing will appy to *.dll as well. I think this is probably the
reason why win32.mak has PDB:NONE definition regardless to /DEBUG
option.
I'll play with it to see how it works, but I'm not an expert of
Microsoft/Windows stuffs, so I'd love to hear from anyone who is more
knowlegeable about this type of topic.
Regards,
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
+----+----+
|.. .| | Motonori Shindo
|_~__| |
| .. |~~_~| Sr. Systems Engineer
| . | | CoSine Communications Inc.
+----+----+
C o S i n e e-mail: mshindo@xxxxxxxxxxxxx
Communications
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
