summaryrefslogtreecommitdiff
path: root/src/common/backtrace.h
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2013-07-19 22:47:49 -0400
committerNick Mathewson <nickm@torproject.org>2013-11-18 10:43:15 -0500
commitbd8ad674b913582b6f8e5b85ac722e14598d681b (patch)
tree6833bbd938ce99a8d8c91bd8f6e53befdd149711 /src/common/backtrace.h
parentb0023083c413c6447ef34cf3c6cfaf54a1cc8793 (diff)
downloadtor-bd8ad674b913582b6f8e5b85ac722e14598d681b.tar.gz
tor-bd8ad674b913582b6f8e5b85ac722e14598d681b.zip
Add a sighandler-safe logging mechanism
We had accidentially grown two fake ones: one for backtrace.c, and one for sandbox.c. Let's do this properly instead. Now, when we configure logs, we keep track of fds that should get told about bad stuff happening from signal handlers. There's another entry point for these that avoids using non-signal-handler-safe functions.
Diffstat (limited to 'src/common/backtrace.h')
-rw-r--r--src/common/backtrace.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/common/backtrace.h b/src/common/backtrace.h
index bb2396080a..7d7c10a800 100644
--- a/src/common/backtrace.h
+++ b/src/common/backtrace.h
@@ -5,7 +5,7 @@
#define TOR_BACKTRACE_H
void dump_backtrace(const char *msg);
-int configure_backtrace_handler(const char *filename, const char *tor_version);
+int configure_backtrace_handler(const char *tor_version);
void clean_up_backtrace_handler(void);
#endif