SuccessChanges

Summary

  1. [StackProtector] Fix crash with vararg due to not checking LocationSize validity. (details)
  2. [debugserver] Fix that debugserver's stop reply packets always return signal code 0 (details)
Commit 2878ecc90f1f22cf0b96c04a4124122db008a2a9 by Amara Emerson
[StackProtector] Fix crash with vararg due to not checking LocationSize validity.

Differential Revision: https://reviews.llvm.org/D87074
The file was modifiedllvm/lib/CodeGen/StackProtector.cpp (diff)
The file was addedllvm/test/CodeGen/X86/stack-guard-memloc-vararg.ll
Commit f0699d9109143754088c26604c58f5ab3e9d4678 by Raphael Isemann
[debugserver] Fix that debugserver's stop reply packets always return signal code 0

If our process terminates due to an unhandled signal, we are supposed to get the
signal code via WTERMSIG. However, we instead try to get the exit status via
WEXITSTATUS which just ends up always calculating signal code 0 (at least on the
macOS implementation where it just shifts the signal code bits away and we're
left with only 0 bits).

The exit status calculation on the LLDB side also seems a bit off as it claims
an exit status that is just the signal code (instead of for example 128 + signal
code), but that will be another patch.

Reviewed By: jasonmolenda

Differential Revision: https://reviews.llvm.org/D86336
The file was addedlldb/test/Shell/Process/TestAbortExitCode.test
The file was addedlldb/test/Shell/Process/Inputs/abort.c
The file was modifiedlldb/tools/debugserver/source/RNBRemote.cpp (diff)