Siddhartha Prakash Jain found a case with a bad resolve that we didn't

properly bail out from, when using ares.

diff --git a/lib/hostip.c b/lib/hostip.c
index 5a7ef2a4c041d540a975f273538fa2f3eee06c2a..5f2a46e7a00cae6742f95a709bc5c47d7c16b65e 100644 (file)
--- a/lib/hostip.c
+++ b/lib/hostip.c
@@ -280,6 +280,7 @@ int Curl_resolv(struct connectdata *conn,
   ssize_t entry_len;
   int wait;
   struct SessionHandle *data = conn->data;
+  CURLcode result;
 
   /* default to failure */
   int rc = -1;
@@ -327,7 +328,9 @@ int Curl_resolv(struct connectdata *conn,
         /* the response to our resolve call will come asynchronously at 
            a later time, good or bad */
         /* First, check that we haven't received the info by now */
-        (void)Curl_is_resolved(conn, &dns);
+        result = Curl_is_resolved(conn, &dns);
+        if(result) /* error detected */
+          return -1;
         if(dns)
           rc = 0; /* pointer provided */
         else