From: guilherme linhares <guilherme.linhares_at_digitro.com.br>
Date: Tue, 25 Oct 2011 08:56:25 -0200

Daniel.

Probably this problem occurs when I call curl_multi_perform simultaneously in multiple threads.
You may want to make a protection for this.

[gui@dgtbn workdir]$ curl-config --version
libcurl 7.19.4
[gui@dgtbn workdir]$ curl-config --vernum
071304

Regards

Guilherme

Em 24/10/2011 18:40, Daniel Stenberg escreveu:

On Mon, 24 Oct 2011, guilherme linhares wrote:

== Info: Connected to 192.168.160.158 (192.168.160.158) port 443 (#2)
== Info: Connected to 192.168.160.158 (192.168.160.158) port 443 (#2)
== Info: SSLv3, TLS handshake, Client hello (1):
== Info: SSLv3, TLS handshake, Client hello (1):
== Info: Unknown SSL protocol error in connection to 192.168.160.158:443
== Info: Expire cleared
== Info: Closing connection #2

This error generated a cored dump

That looks really weird. Does it work if you run it as just a single thread? What resolver backend is your libcurl built to use?

Can you provide us with a complete source code we can use to repeat this problem against a recent libcurl?

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2011-10-25