It looks like my patch didn't make it into the ticket? Here it is again, and inline as well. Sorry for the duplication.

--- a/lib/asyn-thread.c
+++ b/lib/asyn-thread.c
@@ -518,12 +518,13 @@ CURLcode Curl_resolver_is_resolved(struct connectdata *conn,
 
   if(done) {
     getaddrinfo_complete(conn);
- destroy_async_data(&conn->async);
 
     if(!conn->async.dns) {
       resolver_error(conn, "host");
+ destroy_async_data(&conn->async);
       return CURLE_COULDNT_RESOLVE_HOST;
     }
+ destroy_async_data(&conn->async);
     *entry = conn->async.dns;
   }
   else {

Attachment: asyn-thread.patch (542 Bytes; text/x-patch)

---
** [bugs:#1191] When using a wrong hostname in --interface, the wrong host name appears in the error message**
**Status:** open-confirmed
**Created:** Sun Feb 10, 2013 11:30 PM UTC by Kim Vandry
**Last Updated:** Mon Feb 18, 2013 06:37 PM UTC
**Owner:** Daniel Stenberg
While testing my patch for #1189 I discovered a related problem which is pre-existing: I can reproduce it on the current git master. For test 1084, even though the exit code is correct (45, CURLE_INTERFACE_FAILED) the error text is wrong and confusing:
src/curl --interface DoesNotExist.example.com http://www.google.com/
curl: (45) Could not resolve host: www.google.com (Domain name not found)
Actually it failed to resolve DoesNotExist.example.com, not www.google.com like the error message says. If you use --proxy then the error message says "Could not resolve proxy" which is also not true.
I am not sure what the best way to fix this would be (I can think of a hack or two), but I just wanted to document it single I noticed it.
---
Sent from sourceforge.net because you indicated interest in <https://sourceforge.net/p/curl/bugs/1191/>
To unsubscribe from further messages, please visit <https://sourceforge.net/auth/prefs/>