On 25/07/15 01:03, Daniel Stenberg wrote:
If Curl_getconnectinfo() would not not just care about lastconnect
socket, but also would retrieve the connection that is actually being
used, my approach would work. This was suggested in
https://github.com/bagder/curl/pull/86, but was never merged.
On Wed, Jul 29, 2015 at 5:20 PM Daniel Stenberg dan...@haxx.se wrote:
If I install 7.37.0 or greater on either platform everything works just
fine.
That fact alone makes me not that interested in investigating the problem
in
the old version...
Sure, I understand. I didn't mean to ask
On Wed, 29 Jul 2015, Eric Ridge wrote:
I'm using libcurl's multi API and it seems certain older versions crash
deep inside the first call to curl_multi_perform().
...
If I install 7.37.0 or greater on either platform everything works just
fine.
That fact alone makes me not that interested
Hi!
I'm using libcurl's multi API and it seems certain older versions crash
deep inside the first call to curl_multi_perform().
On Ubuntu 14.04.1, which comes with curl v7.35.0, the backtrace is:
#0 Curl_num_addresses (addr=0x323a22656761222c) at hostip.c:159
#1 0x7f1eaded8b86 in
