From: Nick Mathewson <nickm@torproject.org>
Date: Mon, 11 Feb 2013 22:32:58 +0000 (-0500)
Subject: Don't tor_close_socket(-1) in tor-resolve.
X-Git-Tag: tor-0.2.4.11-alpha~33
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=e5a987fbb8cd5574be392abed3e9f5f366dacc47;p=thirdparty%2Ftor.git

Don't tor_close_socket(-1) in tor-resolve.

Bugfix on 96b1bd4fb8e64.  Not in any released Tor.
---

diff --git a/src/tools/tor-resolve.c b/src/tools/tor-resolve.c
index 9b3aa98d1d..306f6c66ab 100644
--- a/src/tools/tor-resolve.c
+++ b/src/tools/tor-resolve.c
@@ -201,7 +201,7 @@ do_resolve(const char *hostname, uint32_t sockshost, uint16_t socksport,
   s = tor_open_socket(PF_INET,SOCK_STREAM,IPPROTO_TCP);
   if (s<0) {
     log_sock_error("creating_socket", -1);
-    goto err;
+    return -1;
   }
 
   memset(&socksaddr, 0, sizeof(socksaddr));