All,
From: Motonori Shindo <mshindo@xxxxxxxxxxx>
Subject: Re: [Ethereal-dev] Re: How do I get .pdb file under Win32
Date: Wed, 12 Dec 2001 14:50:17 +0900 (JST)
> 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 intentionally added a piece of code that would cause a segfault
(char *p=NULL; *p=0;) and examined how Ethereal built with PDB:NONE
and without PDB:NONE worked. In either case, Dr.Watson didn't give me
the right place of the fault (i.e. stack back trace). However, on a
machine that has MSVC++6.0 installed, it gave me the right stack back
trace regardless to with or without PDB:NONE option.
I am a bit confused here.. I may be doing something wrong in using
Dr.Watson. I didn't touch any parameters of Dr.Watson; I'm using it as
it is.
Besides Dr.Watson issue, it looks like we are able to get rid of
separate *.pdb files anyway, but before I do that, I'd love to hear
from someone expert in this area.
Regards,
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
+----+----+
|.. .| | Motonori Shindo
|_~__| |
| .. |~~_~| Sr. Systems Engineer
| . | | CoSine Communications Inc.
+----+----+
C o S i n e e-mail: mshindo@xxxxxxxxxxxxx
Communications
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=