[all-commits] [llvm/llvm-project] 010751: [lldb] Implement CrashReason using UnixSignals

[David Spickett via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 0107513fe79da7670e37c29c0862794a2213a89c
      https://github.com/llvm/llvm-project/commit/0107513fe79da7670e37c29c0862794a2213a89c
  Author: David Spickett <david.spickett at linaro.org>
  Date:   2023-03-20 (Mon, 20 Mar 2023)

  Changed paths:
    M lldb/include/lldb/Target/UnixSignals.h
    M lldb/source/Plugins/Process/POSIX/CrashReason.cpp
    M lldb/source/Plugins/Process/Utility/FreeBSDSignals.cpp
    M lldb/source/Plugins/Process/Utility/LinuxSignals.cpp
    M lldb/source/Plugins/Process/Utility/NetBSDSignals.cpp
    M lldb/source/Target/UnixSignals.cpp
    M lldb/unittests/Signals/UnixSignalsTest.cpp

  Log Message:
  -----------
  [lldb] Implement CrashReason using UnixSignals

By adding signal codes to UnixSignals and adding a new function
where you can get a string with optional address and bounds.

Added signal codes to the Linux, FreeBSD and NetBSD signal sets.
I've checked the numbers against the relevant sources.

Each signal code has a code number, description and printing options.
By default you just get the descripton, you can opt into adding either
a fault address or bounds information.

Bounds signals we'll use the description, unless we have the bounds
values in which case we say whether it is an upper or lower bound
issue.

GetCrashReasonString remains in CrashReason because we need it to
be compiled only for platforms with siginfo_t. Ideally it would
move into NativeProcessProtocol, but that is also used
by NativeRegisterContextWindows, where there would be no siginfo_t.

Reviewed By: JDevlieghere

Differential Revision: https://reviews.llvm.org/D146044