aboutsummaryrefslogtreecommitdiff
path: root/src/or/cpuworker.c
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2006-06-06 00:06:52 +0000
committerRoger Dingledine <arma@torproject.org>2006-06-06 00:06:52 +0000
commit5c57348acdfe97593da260ca98dd88ab4727f2df (patch)
tree97926f4d0d09183f28283e223e487d27e83f22fc /src/or/cpuworker.c
parent411f37d5345d751bbf5fe0b145be1bac63d8d67e (diff)
downloadtor-5c57348acdfe97593da260ca98dd88ab4727f2df.tar
tor-5c57348acdfe97593da260ca98dd88ab4727f2df.tar.gz
We got an obscure report of an assert error on a windows Tor server with
connection_add being called with socket = -1. The only places I can see where that happen would be if our tor_socketpair succeeds but it hands back negative values for some of its file descriptors. Perhaps this will produce more useful assert errors next time. svn:r6550
Diffstat (limited to 'src/or/cpuworker.c')
-rw-r--r--src/or/cpuworker.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/src/or/cpuworker.c b/src/or/cpuworker.c
index badca3563..29fd992f6 100644
--- a/src/or/cpuworker.c
+++ b/src/or/cpuworker.c
@@ -329,6 +329,9 @@ spawn_cpuworker(void)
return -1;
}
+ tor_assert(fdarray[0] >= 0);
+ tor_assert(fdarray[1] >= 0);
+
fd = fdarray[0];
spawn_func(cpuworker_main, (void*)fdarray);
log_debug(LD_OR,"just spawned a cpu worker.");