[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [tor/master] Don't tor_close_socket(-1) in tor-resolve.
commit e5a987fbb8cd5574be392abed3e9f5f366dacc47
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date: Mon Feb 11 17:32:58 2013 -0500
Don't tor_close_socket(-1) in tor-resolve.
Bugfix on 96b1bd4fb8e64. Not in any released Tor.
---
src/tools/tor-resolve.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/tools/tor-resolve.c b/src/tools/tor-resolve.c
index 9b3aa98..306f6c6 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));
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits