aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2013-11-18 10:48:08 -0500
committerNick Mathewson <nickm@torproject.org>2013-11-18 10:48:14 -0500
commitc81f64ab44f71a97649a44e10d6fcbf15aa8c835 (patch)
treee0fa4807ff2219f6407fb277acac1b525e1d8a93
parentc2dfae78d3a881af7cfe2fb4a79da7e3598788fc (diff)
downloadtor-c81f64ab44f71a97649a44e10d6fcbf15aa8c835.tar
tor-c81f64ab44f71a97649a44e10d6fcbf15aa8c835.tar.gz
Improve backtrace changes file
-rw-r--r--changes/stack_trace10
1 files changed, 6 insertions, 4 deletions
diff --git a/changes/stack_trace b/changes/stack_trace
index dc6363887..2eaf15ec8 100644
--- a/changes/stack_trace
+++ b/changes/stack_trace
@@ -1,6 +1,8 @@
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.
+ - On some platforms (currently: recent OSX versions, glibc-based
+ platforms that support the ELF format, and a few other
+ Unix-like operating systems), Tor can now dump stack traces
+ when a crash occurs or an assertion fails. By default, traces
+ are dumped to stderr (if possible) and to any logs that are
+ reporting errors.