On Fri, 18 May 2018, Sean Miller wrote:
Does it seem like that could be what happens in your case? If so, I'll
write up a patch you can test...
I'd be happy to test a patch. I've been poking around in the code a little
myself, but I'm unfamiliar with it.
I've reproduced this on libcurl-7.19.7 (RHEL6... I know...) and
libcurl-7.55.1, the latter of which I build myself.
Hi again, sorry it took me while to get back but attached here is a debug
patch that I'd like you to apply to your code and see what debug output (and
possibly changed behavior) you get. Please do another log and attach in a
reply.
I think might be easiest if you build 7.60.0 (or just git master) from source
if we need to try out further stuff, but I won't insist on putting that on
you. It would also reduce the risk that you're actually seeing the effects of
a bug we've already fixed or subtly changed since 7.55.1...
--
/ daniel.haxx.se
From a03eb7f616218c207b662868fbdc2579a2c8a35a Mon Sep 17 00:00:00 2001
From: Daniel Stenberg <dan...@haxx.se>
Date: Thu, 24 May 2018 00:21:37 +0200
Subject: [PATCH] debug: Curl_protocol_getsock
---
lib/url.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/lib/url.c b/lib/url.c
index 701f83ab3..fdb84267b 100644
--- a/lib/url.c
+++ b/lib/url.c
@@ -1552,11 +1552,14 @@ int Curl_protocol_getsock(struct connectdata *conn,
curl_socket_t *socks,
int numsocks)
{
if(conn->handler->proto_getsock)
return conn->handler->proto_getsock(conn, socks, numsocks);
- return GETSOCK_BLANK;
+ infof(conn->data, "%s:%d => debug point\n",
+ __FILE__, __LINE__);
+ socks[0] = conn->sock[FIRSTSOCKET];
+ return GETSOCK_READSOCK(0) | GETSOCK_WRITESOCK(0);
}
int Curl_doing_getsock(struct connectdata *conn,
curl_socket_t *socks,
int numsocks)
--
2.17.0
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
