1
0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-11-23 11:13:28 +01:00
llvm-mirror/lib/Support/Unix
Mehdi Amini ded74e922b Hint how to get a symbolized stack trace if llvm-symbolizer is not found on crashes
Most users of LLVM tools hit the raw traces and don't know how to get LLVM to
symbolize automatically for them.

When we print the non-symbolized stack trace, we will add information about
how to get it symbolized.

Reviewed By: MaskRay

Differential Revision: https://reviews.llvm.org/D88269
2020-09-25 01:52:20 +00:00
..
COM.inc
DynamicLibrary.inc
Host.inc
Memory.inc
Path.inc Revert "[Modules] Add stats to measure performance of building and loading modules." 2020-09-24 12:36:06 -07:00
Process.inc [CMake] Use find_library for ncurses 2020-08-31 20:06:21 -07:00
Program.inc
README.txt
Signals.inc Hint how to get a symbolized stack trace if llvm-symbolizer is not found on crashes 2020-09-25 01:52:20 +00:00
Threading.inc
ThreadLocal.inc
Unix.h
Watchdog.inc

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.