diff options
| author | Kuba Brecka <kuba.brecka@gmail.com> | 2015-01-22 23:36:47 +0000 |
|---|---|---|
| committer | Kuba Brecka <kuba.brecka@gmail.com> | 2015-01-22 23:36:47 +0000 |
| commit | 405de4ae106cc989f81eafa262a0f324f2732a84 (patch) | |
| tree | 7a6ca5086c9c23dbb07a41ca1e1f89c8f2775bd9 /llvm/tools/llvm-objdump/llvm-objdump.cpp | |
| parent | 495523e4ea3a4619b4f3e49419dbd45060a3c7fb (diff) | |
| download | llvm-405de4ae106cc989f81eafa262a0f324f2732a84.zip llvm-405de4ae106cc989f81eafa262a0f324f2732a84.tar.gz llvm-405de4ae106cc989f81eafa262a0f324f2732a84.tar.bz2 | |
Fix/workaround for OS X truncated stacktraces taken by external tools
This patch is a proposed solution for https://code.google.com/p/address-sanitizer/issues/detail?id=375:
When the stacktraces are captured and printed by ASan itself, they are fine, but when the program has already printed the report (or is just printing it), capturing a stacktrace via other means is broken. "Other means" include OS X CrashReporter, debuggers or calling backtrace() within the program. For example calling backtrace() from a sanitizer_set_death_callback function prints a very truncated stacktrace.
Reviewed at http://reviews.llvm.org/D7103
llvm-svn: 226878
Diffstat (limited to 'llvm/tools/llvm-objdump/llvm-objdump.cpp')
0 files changed, 0 insertions, 0 deletions