Hello all,

I'm having a segmentation fault while using libcurl with the easy interface,
it is a multithread application.

First curl_global_init is called, before starting any thread, then there's a
function that calls curl_easy_init, some curl_easy_setopt, curl_easy_perform
and finally curl_easy_cleanup.

The function is called from different threads.

The backtrace from gdb:

(gdb) bt
#0 0x000000334fa21ca2 in curl_escape () from /usr/lib64/libcurl.so.3
#1 0x000000334fa2212f in curl_msnprintf () from /usr/lib64/libcurl.so.3
#2 0x000000334fa23535 in curl_mvsnprintf () from /usr/lib64/libcurl.so.3
#3 0x000000334fa12e5f in Curl_failf () from /usr/lib64/libcurl.so.3
#4 0x000000334fa0bef3 in Curl_resolv () from /usr/lib64/libcurl.so.3
#5 0x0000000000000000 in ?? ()

At first I thought that it may be related to this:
http://curl.haxx.se/mail/tracker-2008-03/0005.html but I upgrade to 7.21.1 and
it still happens from time to time.

I know this backtrace is almost useless, but (while I get the debug symbols)
is there something I should be aware of? the options used in curl_easy_setopt
are: CURLOPT_URL, CURLOPT_VERBOSE, CURLOPT_TIMEOUT, CURLOPT_HTTPHEADER,
CURLOPT_WRITEFUNCTION, CURLOPT_WRITEDATA.

Thanks

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2010-08-21