aboutsummaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2014-02-24 12:15:32 -0500
committerNick Mathewson <nickm@torproject.org>2014-02-24 12:15:32 -0500
commita3ab31f5dc55b2edde9436f6fb5f990548950702 (patch)
tree472e1cc0365d66386162cee47393f27ba3555b71 /changes
parent1753975ece98f4054ec65683862db120a3b8f261 (diff)
downloadtor-a3ab31f5dc55b2edde9436f6fb5f990548950702.tar
tor-a3ab31f5dc55b2edde9436f6fb5f990548950702.tar.gz
Threadproof our log_backtrace implementation
It's possible for two threads to hit assertion failures at the same time. If that happens, let's keep them from stomping on the same cb_buf field. Fixes bug 11048; bugfix on 0.2.5.2-alpha. Reported by "cypherpunks".
Diffstat (limited to 'changes')
-rw-r--r--changes/bug110488
1 files changed, 8 insertions, 0 deletions
diff --git a/changes/bug11048 b/changes/bug11048
new file mode 100644
index 000000000..684abf959
--- /dev/null
+++ b/changes/bug11048
@@ -0,0 +1,8 @@
+ o Minor bugfixes:
+
+ - Avoid strange behavior if two threads hit failed asswertions
+ at the same time and both try to log backtraces at
+ once. (Previously, if this had happened, both threads would
+ have stored their intermediate results in the same buffer, and
+ generated junk outputs.) Reported by "cypherpunks". Fixes bug
+ 11048; bugfix on 0.2.5.2-alpha.