nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-11 21:53:48 +01:00
Code Issues Packages Projects Releases Wiki Activity
f4864d37ec
tor/src/common/backtrace.h

22 lines
582 B
C
Raw Normal View History

Bump copyright dates to 2015, in case someday this matters.
2015-01-02 20:27:39 +01:00
/* Copyright (c) 2013-2015, The Tor Project, Inc. */
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.
2013-07-19 20:09:58 +02:00
/* See LICENSE for licensing information */
#ifndef TOR_BACKTRACE_H
#define TOR_BACKTRACE_H
Log a backtrace when the sandbox finds a failure This involves some duplicate code between backtrace.c and sandbox.c, but I don't see a way around it: calling more functions would mean adding more steps to our call stack, and running clean_backtrace() against the wrong point on the stack.
2014-04-10 21:44:52 +02:00
#include "orconfig.h"
Make backtrace handler handle signals correctly. This meant moving a fair bit of code around, and writing a signal cleanup function. Still pretty nice from what I can tell, though.
2013-07-26 13:22:56 +02:00
void log_backtrace(int severity, int domain, const char *msg);
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.
2013-07-20 04:47:49 +02:00
int configure_backtrace_handler(const char *tor_version);
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.
2013-07-19 20:09:58 +02:00
void clean_up_backtrace_handler(void);
Log a backtrace when the sandbox finds a failure This involves some duplicate code between backtrace.c and sandbox.c, but I don't see a way around it: calling more functions would mean adding more steps to our call stack, and running clean_backtrace() against the wrong point on the stack.
2014-04-10 21:44:52 +02:00
#ifdef EXPOSE_CLEAN_BACKTRACE
Only expose clean_backtrace() if we'll implement it Fixes windows compilation; bug not in any released Tor. Bugfix on cc9e86db.
2014-04-17 04:00:13 +02:00
#if defined(HAVE_EXECINFO_H) && defined(HAVE_BACKTRACE) && \
defined(HAVE_BACKTRACE_SYMBOLS_FD) && defined(HAVE_SIGACTION)
Fix backtrace compilation on FreeBSD On FreeBSD backtrace(3) uses size_t instead of int (as glibc does). This causes integer precision loss errors when we used int to store its results. The issue is fixed by using size_t to store the results of backtrace(3). The manual page of glibc does not mention that backtrace(3) returns negative values. Therefore, no unsigned integer wrapping occurs when its result is stored in an unsigned data type.
2015-12-15 16:30:04 +01:00
void clean_backtrace(void **stack, size_t depth, const ucontext_t *ctx);
Log a backtrace when the sandbox finds a failure This involves some duplicate code between backtrace.c and sandbox.c, but I don't see a way around it: calling more functions would mean adding more steps to our call stack, and running clean_backtrace() against the wrong point on the stack.
2014-04-10 21:44:52 +02:00
#endif
Only expose clean_backtrace() if we'll implement it Fixes windows compilation; bug not in any released Tor. Bugfix on cc9e86db.
2014-04-17 04:00:13 +02:00
#endif
Log a backtrace when the sandbox finds a failure This involves some duplicate code between backtrace.c and sandbox.c, but I don't see a way around it: calling more functions would mean adding more steps to our call stack, and running clean_backtrace() against the wrong point on the stack.
2014-04-10 21:44:52 +02:00
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.
2013-07-19 20:09:58 +02:00
#endif
Reference in New Issue Copy Permalink