aboutsummaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2010-11-19 22:22:43 -0500
committerNick Mathewson <nickm@torproject.org>2010-11-19 22:22:43 -0500
commit6199ac5fbec7f8a862440a8b65f7f299de4c2dbf (patch)
tree4bbb1629fde78b71981ec4205e65927023b3efea /changes
parenta33b338c5bf5e40037f465c0257a70dedb095e82 (diff)
downloadtor-6199ac5fbec7f8a862440a8b65f7f299de4c2dbf.tar
tor-6199ac5fbec7f8a862440a8b65f7f299de4c2dbf.tar.gz
Do not send Libevent log messages to a controller.
Doing so could make Libevent call Libevent from inside a Libevent logging call, which is a recipe for reentrant confusion and hard-to-debug crashes. This would especially hurt if Libevent debug-level logging is enabled AND the user has a controller watching for low-severity log messages. Fix bug 2190; fix on 0.1.0.2-rc.
Diffstat (limited to 'changes')
-rw-r--r--changes/bug21906
1 files changed, 6 insertions, 0 deletions
diff --git a/changes/bug2190 b/changes/bug2190
new file mode 100644
index 000000000..92ecba7eb
--- /dev/null
+++ b/changes/bug2190
@@ -0,0 +1,6 @@
+ o Minor bugfixes
+ - Prevent calls from Libevent from inside Libevent log handlers.
+ This had potential to cause a nasty set of crashes, especially if
+ running Libevent with debug logging enabled, and running Tor
+ with a controller watching for low-severity log messages.
+ Bugfix on 0.1.0.2-rc. Fixes bug 2190.