mac processor: Add mapping for EXC_BAD_ACCESS/KERN_CODESIGN_ERROR
This code indicates termination under “kill” semantics due to a module’s code signature becoming invalid. Bug: chromium:1023239 Change-Id: I3d453af9ef6c6925edcf9c08dbd78e563877522f Reviewed-on: https://chromium-review.googlesource.com/c/breakpad/breakpad/+/1930177 Reviewed-by: Robert Sesek <rsesek@chromium.org>
This commit is contained in:
parent
62f10f30ba
commit
f6fe7cc55a
2 changed files with 5 additions and 0 deletions
|
@ -87,6 +87,8 @@ typedef enum {
|
|||
/* KERN_MEMORY_FAILURE */
|
||||
MD_EXCEPTION_CODE_MAC_MEMORY_ERROR = 10,
|
||||
/* KERN_MEMORY_ERROR */
|
||||
MD_EXCEPTION_CODE_MAC_CODESIGN_ERROR = 50,
|
||||
/* KERN_CODESIGN_ERROR */
|
||||
|
||||
/* With MD_EXCEPTION_SOFTWARE */
|
||||
MD_EXCEPTION_CODE_MAC_BAD_SYSCALL = 0x00010000, /* Mach SIGSYS */
|
||||
|
|
|
@ -804,6 +804,9 @@ string MinidumpProcessor::GetCrashReason(Minidump *dump, uint64_t *address) {
|
|||
case MD_EXCEPTION_CODE_MAC_MEMORY_ERROR:
|
||||
reason.append("KERN_MEMORY_ERROR");
|
||||
break;
|
||||
case MD_EXCEPTION_CODE_MAC_CODESIGN_ERROR:
|
||||
reason.append("KERN_CODESIGN_ERROR");
|
||||
break;
|
||||
default:
|
||||
// arm and ppc overlap
|
||||
if (raw_system_info->processor_architecture ==
|
||||
|
|
Loading…
Reference in a new issue