2013-05-18 00:17:19 +08:00
|
|
|
//===-- sanitizer_common_libcdep.cc ---------------------------------------===//
|
|
|
|
//
|
|
|
|
// The LLVM Compiler Infrastructure
|
|
|
|
//
|
|
|
|
// This file is distributed under the University of Illinois Open Source
|
|
|
|
// License. See LICENSE.TXT for details.
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
//
|
|
|
|
// This file is shared between AddressSanitizer and ThreadSanitizer
|
|
|
|
// run-time libraries.
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
|
|
|
#include "sanitizer_common.h"
|
Reapply: [asan] On OS X, log reports to syslog and os_trace
When ASan currently detects a bug, by default it will only print out the text
of the report to stderr. This patch changes this behavior and writes the full
text of the report to syslog before we terminate the process. It also calls
os_trace (Activity Tracing available on OS X and iOS) with a message saying
that the report is available in syslog. This is useful, because this message
will be shown in the crash log.
For this to work, the patch makes sure we store the full report into
error_message_buffer unconditionally, and it also strips out ANSI escape
sequences from the report (they are used when producing colored reports).
I've initially tried to log to syslog during printing, which is done on Android
right now. The advantage is that if we crash during error reporting or the
produced error does not go through ScopedInErrorReport, we would still get a
(partial) message in the syslog. However, that solution is very problematic on
OS X. One issue is that the logging routine uses GCD, which may spawn a new
thread on its behalf. In many cases, the reporting logic locks threadRegistry,
which leads to deadlocks.
Reviewed at http://reviews.llvm.org/D13452
(In addition, add sanitizer_common_libcdep.cc to buildgo.sh to avoid
build failures on Linux.)
llvm-svn: 253688
2015-11-21 02:41:44 +08:00
|
|
|
#include "sanitizer_allocator_internal.h"
|
2014-02-26 17:06:59 +08:00
|
|
|
#include "sanitizer_flags.h"
|
2014-12-17 03:13:01 +08:00
|
|
|
#include "sanitizer_stackdepot.h"
|
2014-09-11 06:45:09 +08:00
|
|
|
#include "sanitizer_stacktrace.h"
|
|
|
|
#include "sanitizer_symbolizer.h"
|
2013-05-18 00:17:19 +08:00
|
|
|
|
2015-04-09 01:08:24 +08:00
|
|
|
#if SANITIZER_POSIX
|
|
|
|
#include "sanitizer_posix.h"
|
|
|
|
#endif
|
|
|
|
|
2013-05-18 00:17:19 +08:00
|
|
|
namespace __sanitizer {
|
|
|
|
|
2015-04-09 01:42:57 +08:00
|
|
|
bool ReportFile::SupportsColors() {
|
2014-12-12 02:30:25 +08:00
|
|
|
SpinMutexLock l(mu);
|
|
|
|
ReopenIfNecessary();
|
2015-04-09 01:42:57 +08:00
|
|
|
return SupportsColoredOutput(fd);
|
2013-05-18 00:17:19 +08:00
|
|
|
}
|
|
|
|
|
2014-12-12 02:30:25 +08:00
|
|
|
bool ColorizeReports() {
|
2013-09-03 21:31:03 +08:00
|
|
|
// FIXME: Add proper Windows support to AnsiColorDecorator and re-enable color
|
|
|
|
// printing on Windows.
|
|
|
|
if (SANITIZER_WINDOWS)
|
2014-12-12 02:30:25 +08:00
|
|
|
return false;
|
2014-02-26 17:06:59 +08:00
|
|
|
|
|
|
|
const char *flag = common_flags()->color;
|
|
|
|
return internal_strcmp(flag, "always") == 0 ||
|
2015-04-09 01:42:57 +08:00
|
|
|
(internal_strcmp(flag, "auto") == 0 && report_file.SupportsColors());
|
2014-02-26 17:06:59 +08:00
|
|
|
}
|
2014-05-27 20:37:52 +08:00
|
|
|
|
|
|
|
static void (*sandboxing_callback)();
|
|
|
|
void SetSandboxingCallback(void (*f)()) {
|
|
|
|
sandboxing_callback = f;
|
|
|
|
}
|
|
|
|
|
2014-09-11 06:45:09 +08:00
|
|
|
void ReportErrorSummary(const char *error_type, StackTrace *stack) {
|
Reapply: [asan] On OS X, log reports to syslog and os_trace
When ASan currently detects a bug, by default it will only print out the text
of the report to stderr. This patch changes this behavior and writes the full
text of the report to syslog before we terminate the process. It also calls
os_trace (Activity Tracing available on OS X and iOS) with a message saying
that the report is available in syslog. This is useful, because this message
will be shown in the crash log.
For this to work, the patch makes sure we store the full report into
error_message_buffer unconditionally, and it also strips out ANSI escape
sequences from the report (they are used when producing colored reports).
I've initially tried to log to syslog during printing, which is done on Android
right now. The advantage is that if we crash during error reporting or the
produced error does not go through ScopedInErrorReport, we would still get a
(partial) message in the syslog. However, that solution is very problematic on
OS X. One issue is that the logging routine uses GCD, which may spawn a new
thread on its behalf. In many cases, the reporting logic locks threadRegistry,
which leads to deadlocks.
Reviewed at http://reviews.llvm.org/D13452
(In addition, add sanitizer_common_libcdep.cc to buildgo.sh to avoid
build failures on Linux.)
llvm-svn: 253688
2015-11-21 02:41:44 +08:00
|
|
|
#if !SANITIZER_GO
|
2014-09-11 06:45:09 +08:00
|
|
|
if (!common_flags()->print_summary)
|
|
|
|
return;
|
2015-03-18 07:46:06 +08:00
|
|
|
if (stack->size == 0) {
|
|
|
|
ReportErrorSummary(error_type);
|
2015-02-27 10:29:25 +08:00
|
|
|
return;
|
2015-03-18 07:46:06 +08:00
|
|
|
}
|
2015-02-27 10:29:25 +08:00
|
|
|
// Currently, we include the first stack frame into the report summary.
|
|
|
|
// Maybe sometimes we need to choose another frame (e.g. skip memcpy/etc).
|
|
|
|
uptr pc = StackTrace::GetPreviousInstructionPc(stack->trace[0]);
|
|
|
|
SymbolizedStack *frame = Symbolizer::GetOrInit()->SymbolizePC(pc);
|
|
|
|
ReportErrorSummary(error_type, frame->info);
|
|
|
|
frame->ClearAll();
|
Reapply: [asan] On OS X, log reports to syslog and os_trace
When ASan currently detects a bug, by default it will only print out the text
of the report to stderr. This patch changes this behavior and writes the full
text of the report to syslog before we terminate the process. It also calls
os_trace (Activity Tracing available on OS X and iOS) with a message saying
that the report is available in syslog. This is useful, because this message
will be shown in the crash log.
For this to work, the patch makes sure we store the full report into
error_message_buffer unconditionally, and it also strips out ANSI escape
sequences from the report (they are used when producing colored reports).
I've initially tried to log to syslog during printing, which is done on Android
right now. The advantage is that if we crash during error reporting or the
produced error does not go through ScopedInErrorReport, we would still get a
(partial) message in the syslog. However, that solution is very problematic on
OS X. One issue is that the logging routine uses GCD, which may spawn a new
thread on its behalf. In many cases, the reporting logic locks threadRegistry,
which leads to deadlocks.
Reviewed at http://reviews.llvm.org/D13452
(In addition, add sanitizer_common_libcdep.cc to buildgo.sh to avoid
build failures on Linux.)
llvm-svn: 253688
2015-11-21 02:41:44 +08:00
|
|
|
#endif
|
2014-09-11 06:45:09 +08:00
|
|
|
}
|
|
|
|
|
2015-01-07 07:53:32 +08:00
|
|
|
static void (*SoftRssLimitExceededCallback)(bool exceeded);
|
|
|
|
void SetSoftRssLimitExceededCallback(void (*Callback)(bool exceeded)) {
|
|
|
|
CHECK_EQ(SoftRssLimitExceededCallback, nullptr);
|
|
|
|
SoftRssLimitExceededCallback = Callback;
|
|
|
|
}
|
|
|
|
|
2014-12-17 03:13:01 +08:00
|
|
|
void BackgroundThread(void *arg) {
|
|
|
|
uptr hard_rss_limit_mb = common_flags()->hard_rss_limit_mb;
|
2015-01-07 07:53:32 +08:00
|
|
|
uptr soft_rss_limit_mb = common_flags()->soft_rss_limit_mb;
|
2014-12-17 03:13:01 +08:00
|
|
|
uptr prev_reported_rss = 0;
|
|
|
|
uptr prev_reported_stack_depot_size = 0;
|
2015-01-07 07:53:32 +08:00
|
|
|
bool reached_soft_rss_limit = false;
|
2014-12-17 03:13:01 +08:00
|
|
|
while (true) {
|
|
|
|
SleepForMillis(100);
|
|
|
|
uptr current_rss_mb = GetRSS() >> 20;
|
2015-01-20 21:21:20 +08:00
|
|
|
if (Verbosity()) {
|
2014-12-17 03:13:01 +08:00
|
|
|
// If RSS has grown 10% since last time, print some information.
|
|
|
|
if (prev_reported_rss * 11 / 10 < current_rss_mb) {
|
|
|
|
Printf("%s: RSS: %zdMb\n", SanitizerToolName, current_rss_mb);
|
|
|
|
prev_reported_rss = current_rss_mb;
|
|
|
|
}
|
|
|
|
// If stack depot has grown 10% since last time, print it too.
|
|
|
|
StackDepotStats *stack_depot_stats = StackDepotGetStats();
|
|
|
|
if (prev_reported_stack_depot_size * 11 / 10 <
|
|
|
|
stack_depot_stats->allocated) {
|
|
|
|
Printf("%s: StackDepot: %zd ids; %zdM allocated\n",
|
|
|
|
SanitizerToolName,
|
|
|
|
stack_depot_stats->n_uniq_ids,
|
|
|
|
stack_depot_stats->allocated >> 20);
|
|
|
|
prev_reported_stack_depot_size = stack_depot_stats->allocated;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
// Check RSS against the limit.
|
|
|
|
if (hard_rss_limit_mb && hard_rss_limit_mb < current_rss_mb) {
|
|
|
|
Report("%s: hard rss limit exhausted (%zdMb vs %zdMb)\n",
|
|
|
|
SanitizerToolName, hard_rss_limit_mb, current_rss_mb);
|
|
|
|
DumpProcessMap();
|
|
|
|
Die();
|
|
|
|
}
|
2015-01-07 07:53:32 +08:00
|
|
|
if (soft_rss_limit_mb) {
|
|
|
|
if (soft_rss_limit_mb < current_rss_mb && !reached_soft_rss_limit) {
|
|
|
|
reached_soft_rss_limit = true;
|
|
|
|
Report("%s: soft rss limit exhausted (%zdMb vs %zdMb)\n",
|
|
|
|
SanitizerToolName, soft_rss_limit_mb, current_rss_mb);
|
|
|
|
if (SoftRssLimitExceededCallback)
|
|
|
|
SoftRssLimitExceededCallback(true);
|
|
|
|
} else if (soft_rss_limit_mb >= current_rss_mb &&
|
|
|
|
reached_soft_rss_limit) {
|
|
|
|
reached_soft_rss_limit = false;
|
|
|
|
if (SoftRssLimitExceededCallback)
|
|
|
|
SoftRssLimitExceededCallback(false);
|
|
|
|
}
|
|
|
|
}
|
2014-12-17 03:13:01 +08:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
Reapply: [asan] On OS X, log reports to syslog and os_trace
When ASan currently detects a bug, by default it will only print out the text
of the report to stderr. This patch changes this behavior and writes the full
text of the report to syslog before we terminate the process. It also calls
os_trace (Activity Tracing available on OS X and iOS) with a message saying
that the report is available in syslog. This is useful, because this message
will be shown in the crash log.
For this to work, the patch makes sure we store the full report into
error_message_buffer unconditionally, and it also strips out ANSI escape
sequences from the report (they are used when producing colored reports).
I've initially tried to log to syslog during printing, which is done on Android
right now. The advantage is that if we crash during error reporting or the
produced error does not go through ScopedInErrorReport, we would still get a
(partial) message in the syslog. However, that solution is very problematic on
OS X. One issue is that the logging routine uses GCD, which may spawn a new
thread on its behalf. In many cases, the reporting logic locks threadRegistry,
which leads to deadlocks.
Reviewed at http://reviews.llvm.org/D13452
(In addition, add sanitizer_common_libcdep.cc to buildgo.sh to avoid
build failures on Linux.)
llvm-svn: 253688
2015-11-21 02:41:44 +08:00
|
|
|
void WriteToSyslog(const char *buffer) {
|
|
|
|
char *copy = internal_strdup(buffer);
|
|
|
|
char *p = copy;
|
|
|
|
char *q;
|
|
|
|
|
|
|
|
// Remove color sequences since syslogs cannot print them.
|
|
|
|
RemoveANSIEscapeSequencesFromString(copy);
|
|
|
|
|
|
|
|
// Print one line at a time.
|
|
|
|
// syslog, at least on Android, has an implicit message length limit.
|
|
|
|
do {
|
|
|
|
q = internal_strchr(p, '\n');
|
|
|
|
if (q)
|
|
|
|
*q = '\0';
|
|
|
|
WriteOneLineToSyslog(p);
|
|
|
|
if (q)
|
|
|
|
p = q + 1;
|
|
|
|
} while (q);
|
|
|
|
InternalFree(copy);
|
|
|
|
}
|
|
|
|
|
2014-12-17 03:13:01 +08:00
|
|
|
void MaybeStartBackgroudThread() {
|
Reapply: [asan] On OS X, log reports to syslog and os_trace
When ASan currently detects a bug, by default it will only print out the text
of the report to stderr. This patch changes this behavior and writes the full
text of the report to syslog before we terminate the process. It also calls
os_trace (Activity Tracing available on OS X and iOS) with a message saying
that the report is available in syslog. This is useful, because this message
will be shown in the crash log.
For this to work, the patch makes sure we store the full report into
error_message_buffer unconditionally, and it also strips out ANSI escape
sequences from the report (they are used when producing colored reports).
I've initially tried to log to syslog during printing, which is done on Android
right now. The advantage is that if we crash during error reporting or the
produced error does not go through ScopedInErrorReport, we would still get a
(partial) message in the syslog. However, that solution is very problematic on
OS X. One issue is that the logging routine uses GCD, which may spawn a new
thread on its behalf. In many cases, the reporting logic locks threadRegistry,
which leads to deadlocks.
Reviewed at http://reviews.llvm.org/D13452
(In addition, add sanitizer_common_libcdep.cc to buildgo.sh to avoid
build failures on Linux.)
llvm-svn: 253688
2015-11-21 02:41:44 +08:00
|
|
|
#if SANITIZER_LINUX && \
|
|
|
|
!SANITIZER_GO // Need to implement/test on other platforms.
|
2015-01-07 07:53:32 +08:00
|
|
|
// Start the background thread if one of the rss limits is given.
|
|
|
|
if (!common_flags()->hard_rss_limit_mb &&
|
|
|
|
!common_flags()->soft_rss_limit_mb) return;
|
2015-02-18 05:57:42 +08:00
|
|
|
if (!&real_pthread_create) return; // Can't spawn the thread anyway.
|
2014-12-17 03:13:01 +08:00
|
|
|
internal_start_thread(BackgroundThread, nullptr);
|
2015-04-02 22:48:08 +08:00
|
|
|
#endif
|
2014-12-17 03:13:01 +08:00
|
|
|
}
|
|
|
|
|
2013-05-18 00:17:19 +08:00
|
|
|
} // namespace __sanitizer
|
2014-05-27 20:37:52 +08:00
|
|
|
|
|
|
|
void NOINLINE
|
|
|
|
__sanitizer_sandbox_on_notify(__sanitizer_sandbox_arguments *args) {
|
|
|
|
PrepareForSandboxing(args);
|
|
|
|
if (sandboxing_callback)
|
|
|
|
sandboxing_callback();
|
|
|
|
}
|