From 7363eae13cb8febd85923957de19e2de7c186cea Mon Sep 17 00:00:00 2001
From: Nick Mathewson <nickm@torproject.org>
Date: Mon, 14 Nov 2011 17:46:43 -0500
Subject: Use the EVENT_BASE_FLAG_NOLOCK flag to prevent socketpair()
 invocation

In Tor 0.2.2, we never need the event base to be notifiable, since we
don't call it from other threads.  This is a workaround for bug 4457,
which is not actually a Tor bug IMO.
---
 changes/bug4457 | 8 ++++++++
 1 file changed, 8 insertions(+)
 create mode 100644 changes/bug4457

(limited to 'changes')

diff --git a/changes/bug4457 b/changes/bug4457
new file mode 100644
index 000000000..d3d9eb3b4
--- /dev/null
+++ b/changes/bug4457
@@ -0,0 +1,8 @@
+  o Minor bugfixes:
+    - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
+      that it doesn't attempt to allocate a socketpair. This could cause
+      some problems on windows systems with overzealous firewalls. Fix for
+      bug 4457; workaround for Libevent versions 2.0.1-alpha through
+      2.0.15-stable.
+
+
-- 
cgit v1.2.3