aboutsummaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2013-07-19 14:09:58 -0400
committerNick Mathewson <nickm@torproject.org>2013-11-18 10:43:14 -0500
commit063bea58bcc1c27864a0351bba07254855903377 (patch)
tree8a0f0ea303fbbc4b86d31c54dd9da761f658f4e2 /changes
parentf6d8bc9389db72dc654560d0f86fd3edd3b14934 (diff)
downloadtor-063bea58bcc1c27864a0351bba07254855903377.tar
tor-063bea58bcc1c27864a0351bba07254855903377.tar.gz
Basic backtrace ability
On platforms with the backtrace/backtrace_symbols_fd interface, Tor can now dump stack traces on assertion failure. By default, I log them to DataDir/stack_dump and to stderr.
Diffstat (limited to 'changes')
-rw-r--r--changes/stack_trace6
1 files changed, 6 insertions, 0 deletions
diff --git a/changes/stack_trace b/changes/stack_trace
new file mode 100644
index 000000000..dc6363887
--- /dev/null
+++ b/changes/stack_trace
@@ -0,0 +1,6 @@
+ o Major features:
+ - On some platforms (currently, recent OSX versions, and glibc-based
+ platforms that support the ELF format), Tor can now dump
+ stack traces when an assertion fails. By default, traces are dumped
+ to stderr, and to a stack_dump file in the DataDirectory.
+