Correct formatting in util/posix/signals_test.cc

Change-Id: I431f663a91bfce62b8d554ee980fa62da8551275
Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3223541
Reviewed-by: Mark Mentovai <mark@chromium.org>
Commit-Queue: Justin Cohen <justincohen@chromium.org>
This commit is contained in:
Justin Cohen 2021-10-14 11:34:57 -04:00 committed by Crashpad LUCI CQ
parent 204abe16d2
commit 02d50376a7

View File

@ -42,9 +42,7 @@ constexpr int kUnexpectedExitStatus = 3;
// Keep synchronized with CauseSignal().
bool CanCauseSignal(int sig) {
return sig == SIGABRT ||
sig == SIGALRM ||
sig == SIGBUS ||
return sig == SIGABRT || sig == SIGALRM || sig == SIGBUS ||
/* According to DDI0487D (Armv8 Architecture Reference Manual) the expected
* behavior for division by zero (Section 3.4.8) is: "... results in a
* zero being written to the destination register, without any
@ -58,8 +56,7 @@ bool CanCauseSignal(int sig) {
#if defined(ARCH_CPU_X86_FAMILY) || defined(ARCH_CPU_ARMEL)
sig == SIGILL ||
#endif // defined(ARCH_CPU_X86_FAMILY) || defined(ARCH_CPU_ARMEL)
sig == SIGPIPE ||
sig == SIGSEGV ||
sig == SIGPIPE || sig == SIGSEGV ||
#if defined(OS_APPLE)
sig == SIGSYS ||
#endif // OS_APPLE