RE: new makefile for Visual C++
Date: Tue, 24 Feb 2009 16:27:08 -0500
Yes, the options do separate things.
/debug maintains the symbol file information to be put into the PDB
/release adds a checksum value to the exe COFF header of the executable
so the debugger can determine which PDB file to use when downloading the
symbol file from a network resource (SMB or HTTP).
I forgot to mention that these should be added for both release and
The basic gist of this allows an application or debugger to download a
symbol file from a web server and dump out its own call stack to a log
file or email to be used by a developer to determine the nature of a
We use the technology in BOINC as a means of tracking and fixing crashes
that happen on our users machines. All we have to do is ask for the log
file, and we skip the step of having them install a debugger or build
from source themselves.
An example symstore can be found here:
A more detailed explanation of symbol stores and symbol servers can be
[mailto:curl-library-bounces_at_cool.haxx.se] On Behalf Of Piotr Dobrogost
Sent: Tuesday, February 24, 2009 2:53 PM
To: libcurl development
Subject: Re: new makefile for Visual C++
Rom Walton wrote:
> Would you all mind adding the following to your Windows makefiles?
> LFLAGS = /debug /release
> Basically those additional flags will prepare the new libcurl builds
> for generating a PDB symbol file which can be added to a symbol store
Both at the same time??
Actually /debug and /pdp: are already present in new version of
117: !IF "$(BUILD_CFG)" == "dynamic-debug"
118: LFLAGS = $(LFLAGS) $(LFLAGS_DYNAMIC) /debug
380: !IF "$(BUILD_CFG)" == "dynamic-debug"
390: LFLAGS = $(LFLAGS) $(LNK_OUT).dll $(LNK_OUT_IMP)
I tried to use it in static-debug build as well but I got errors. Do you
know which build configs it's valid in?
Received on 2009-02-24