Open
Bug 1804299
Opened 3 years ago
Updated 3 years ago
Fuzzing debug build does not launch on M1
Categories
(Firefox Build System :: General, defect, P3)
Tracking
(Not tracked)
NEW
People
(Reporter: truber, Unassigned)
References
Details
Attachments
(1 file)
|
6.81 KB,
text/plain
|
Details |
I recently setup a Mac Mini M1 for fuzzing. The fuzzing-asan build works fine, while the fuzzing-debug build does not.
Hardware Model: Macmini9,1
Process: firefox [3015]
Path: /Users/USER/*/Firefox NightlyDebug.app/Contents/MacOS/firefox
Identifier: org.mozilla.nightlydebug
Version: 109.0a1 (10922.12.6)
Code Type: ARM-64 (Native)
Role: Unspecified
Parent Process: Python [3014]
Coalition: com.googlecode.iterm2 [833]
Responsible Process: iTerm2 [915]
Date/Time: 2022-12-06 13:08:59.4757 -0500
Launch Time: 2022-12-06 13:08:59.4718 -0500
OS Version: macOS 13.0.1 (22A400)
Release Type: User
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid))
Exception Subtype: UNKNOWN_0x32 at 0x00000001001f0000
Exception Codes: 0x0000000000000032, 0x00000001001f0000
VM Region Info: 0x1001f0000 is in 0x1001f0000-0x10022c000; bytes after start: 0 bytes before end: 245759
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
---> mapped file 1001f0000-10022c000 [ 240K] r-x/r-x SM=COW ...t_id=ccb319c7
mapped file 10022c000-100230000 [ 16K] rw-/rw- SM=COW ...t_id=ccb319c7
Termination Reason: CODESIGNING 2 Invalid Page
I can see from bug 1793610 that this might be expected, but I'm wondering why the asan build works.
Comment 1•3 years ago
|
||
The severity field is not set for this bug.
:ahochheiden, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(ahochheiden)
Updated•3 years ago
|
Severity: -- → S3
Flags: needinfo?(ahochheiden)
Priority: -- → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•