I even don't know how to see the diffs on a pull request (sorry), but I can really imagine that making a PDB file is not only useful for debug builds, but also for release builds. In our own case, we are prodiving (stripped) pdb files to customers. That pdb files contain line numbers only (and external function names). If a crash occurs (=fatal exception), then the win dbg API (publically available as part of the Windows SDK) uses the provided pdb files, and a stack trace can be generated (similar to U_STACK_TRACE() on HP and similar to what gstack creates on Linux).
Based on reading my patch, I think that creating a PDB for the DLL is just as easy as adding CFLAGS_PDB to the LNK command. However, I still have doubts about the current structure of the makefile. See my next reply to Rod Kees -----Original Message----- From: curl-library [mailto:curl-library-boun...@cool.haxx.se] On Behalf Of Daniel Stenberg Sent: Monday, January 16, 2017 18:52 To: libcurl development <curl-library@cool.haxx.se> Subject: Re: proposed changes for winbuild makefile On Mon, 16 Jan 2017, Kees Dekker wrote: > I've attached a patch to address some issues in the Windows build. Somewhat related, we have an old outstanding pull request for another winbuild improvement that I would like a windows-build person to give thumbs up to before we can merge (mostly because I don't build on/know Windows myself): https://github.com/curl/curl/pull/730 -- / daniel.haxx.se ------------------------------------------------------------------- List admin: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html ------------------------------------------------------------------- List admin: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
