llvm-project/llvm/lib/Support/Windows
Ben Dunbobbin 7cd1c01c8e [windows][support] Improve backtrace emitted in crash report without llvm-symbolizer
Currently the backtrace emitted on windows when llvm-symbolizer is not
available includes addresses which cannot be easily decoded because
the addresses have the containing module's run-time base address added
into them, but we don't know what those base addresses are. This
change emits a module offset rather than an address.

There are a couple of related changes which were included as a result
of the review discussion for this patch:
- I have also removed the parameter printing as it adds noise to the
  dump and doesn't seem useful.
- I have added the exception code to the backtrace.

Differential Review: https://reviews.llvm.org/D127915
2022-06-20 12:34:32 +01:00
..
COM.inc
DynamicLibrary.inc
Host.inc [NFC] Fix build when LLVM_DEFAULT_TARGET_TRIPLE="" 2022-01-31 13:31:55 -06:00
Memory.inc
Path.inc LLVM Driver Multicall tool 2022-06-06 04:27:32 +00:00
Process.inc [Windows] Don't try to wildcard expand paths starting with \\?\ 2022-06-01 11:25:49 +03:00
Program.inc Cleanup include: TableGen 2022-03-11 11:41:32 +01:00
Signals.inc [windows][support] Improve backtrace emitted in crash report without llvm-symbolizer 2022-06-20 12:34:32 +01:00
ThreadLocal.inc
Threading.inc Add ThreadPriority::Low, and use QoS class Utility on Mac 2022-05-16 10:01:49 +02:00
Watchdog.inc
explicit_symbols.inc