Libcurl (was Re: [Announce] GnuPG 1.4.1 released)

David Shaw dshaw at jabberwocky.com
Tue Mar 22 14:55:36 CET 2005


On Tue, Mar 22, 2005 at 01:15:15PM +0100, Carlo Luciano Bianco wrote:

> [...]
> (gdb) bt
> #0  0x77c16137 in strdup () from C:\WINDOWS\system32\msvcrt.dll
> #1  0x003d52e0 in ?? ()
> #2  0x0022f088 in ?? ()
> #3  0x69f51e6d in libcurl!curl_slist_free_all () from 
> c:\programmi\mingw\bin\libcurl.dll
> --------------------------------------------------------------------------
>  
> > It happened in strdup() so that's usually because the string you are
> > trying to copy (or copy to) is not accessible - maybe not properly
> > initialised. The fault is not necessarily in the file identified above,
> > it just showed up there. Use up and down commands after getting the
> > backtrace to inspect the calls that lead to the segmentation fault.
> 
> The above four are all the frames I get.

The strdup segfault is happening due to a call from inside libcurl
itself.  That doesn't necessarily mean a bug in curl, though.  What
version of curl are you using here?

Also, can you try and rebuild libcurl with -g and no optimization?
Maybe we can get a better stacktrace.

David



More information about the Gnupg-users mailing list