llvm-project/llvm/lib/Support/Unix
Bob Wilson d7bef6972d Use _Unwind_Backtrace on Apple platforms.
Darwin's backtrace() function does not work with sigaltstack (which was
enabled when available with r270395) — it does a sanity check to make
sure that the current frame pointer is within the expected stack area
(which it is not when using an alternate stack) and gives up otherwise.
The alternative of _Unwind_Backtrace seems to work fine on macOS, so use
that when backtrace() fails. Note that we then use backtrace_symbols_fd()
with the addresses from _Unwind_Backtrace, but I’ve tested that and it
also seems to work fine. rdar://problem/28646552

llvm-svn: 286851
2016-11-14 17:56:18 +00:00
..
COM.inc
Host.inc
Memory.inc Correct mprotect page boundries to round up end page. Fixes PR30905. 2016-11-05 04:22:15 +00:00
Mutex.inc
Path.inc [Chrono] Fix !HAVE_FUTIMENS build 2016-10-24 14:19:28 +00:00
Process.inc Zero-initialize chrono duration objects 2016-11-09 11:43:57 +00:00
Program.inc
README.txt
RWMutex.inc
Signals.inc Use _Unwind_Backtrace on Apple platforms. 2016-11-14 17:56:18 +00:00
ThreadLocal.inc
Unix.h Remove TimeValue usage from llvm/Support 2016-10-24 10:59:17 +00:00
Watchdog.inc

README.txt

llvm/lib/Support/Unix README
===========================

This directory provides implementations of the lib/System classes that
are common to two or more variants of UNIX. For example, the directory
structure underneath this directory could look like this:

Unix           - only code that is truly generic to all UNIX platforms
  Posix        - code that is specific to Posix variants of UNIX
  SUS          - code that is specific to the Single Unix Specification
  SysV         - code that is specific to System V variants of UNIX

As a rule, only those directories actually needing to be created should be
created. Also, further subdirectories could be created to reflect versions of
the various standards. For example, under SUS there could be v1, v2, and v3
subdirectories to reflect the three major versions of SUS.