Hi,
From: Motonori Shindo <mshindo@xxxxxxxxxxx>
Subject: Re: [Ethereal-dev] Re: How do I get .pdb file under Win32
Date: Wed, 12 Dec 2001 22:36:59 +0900 (JST)
> 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.
Further investigation revealed that Dr.Watson doesn't seem to be able
to read symbol of the name of "static" function. Since most of the
functions in dissectors are static, what Dr.Watson can tell is
somewhat limited, I think.
> 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.
As to whether we should have separate *.pdb or making
debug-info-embedded *.exe/*.dll, it has pros and cons. If we have
separate *.pdb file, users can choose whether to install these files
on their hard disk or not (and this is what we're currently doing). On
the other hand, if we pursue embedded *.exe/*.dll model, users would
have no choice even if they don't wish to have debugging info. Upside
of this approach is that there are less files to manage and we'll have
a smaller ethereal-setup.exe because *.pdb+*.exe(/wo debug info) is
generally larger than *.exe(embedded) in terms of a total file size.
However, given that we haven't come up with an elegant way how to
generate separate *.pdb files withing the framework that current
win32.mak provides, I personally think that we should go for an
embedded model. Any comment??
Regards,
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
+----+----+
|.. .| | Motonori Shindo
|_~__| |
| .. |~~_~| Sr. Systems Engineer
| . | | CoSine Communications Inc.
+----+----+
C o S i n e e-mail: mshindo@xxxxxxxxxxxxx
Communications
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
