diff options
| author | Nick Mathewson <nickm@torproject.org> | 2010-11-19 22:22:43 -0500 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2010-11-19 22:27:40 -0500 |
| commit | 668f7a2639faf59e5bc4f2615e61e0e768e0b26d (patch) | |
| tree | 65d05f689f883c22995ddc59635f11410a1394e8 /changes | |
| parent | 566a115be1acbd0838c81edd251cf7ae47b94fe3 (diff) | |
| download | tor-668f7a2639faf59e5bc4f2615e61e0e768e0b26d.tar.gz tor-668f7a2639faf59e5bc4f2615e61e0e768e0b26d.zip | |
Do not send Libevent log messages to a controller (0.2.1 backport)
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/bug2190 | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/changes/bug2190 b/changes/bug2190 new file mode 100644 index 0000000000..92ecba7eb0 --- /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. |