[MacPorts] #60818: darwintrace cannot inject into binaries of a different architecture (missing arm64e)
MacPorts
noreply at macports.org
Fri Jul 24 10:24:23 UTC 2026
#60818: darwintrace cannot inject into binaries of a different architecture
(missing arm64e)
--------------------------+-----------------------
Reporter: saagarjha | Owner: (none)
Type: enhancement | Status: reopened
Priority: Normal | Milestone:
Component: base | Version:
Resolution: | Keywords: tracemode
Port: |
--------------------------+-----------------------
Comment (by fpottbaecker):
Replying to [comment:5 raimue]:
> The missing part is `arm64e`, which is a new ABI to support Pointer
Authentication as specified with ARMv8.3.
>
>
https://developer.apple.com/documentation/security/preparing_your_app_to_work_with_pointer_authentication
>
> However, Apple does not consider this ABI as stable. The use of arm64e
seems to be limited to binaries signed by Apple. As I have read, it is
actually used in binaries in `/usr/bin` but I cannot confirm this. I
assume (!) this limitation also applies to libraries and therefore we
cannot just build darwintrace.dylib for arm64e and inject it into the
process.
As far as I can tell, the ABI has been stabilized last year, and the
linked article does not make any reference to the application needing
specific entitlements/notarozation/....
I am running into this issue now trying to investigate an xcodebuild
failure in a Portfile I am writing, and maybe this is worth looking into
again? I would be happy to jump in here, but could use a few pointers, as
I am not too familiar with autoconf and would take some time to figure out
how to properly validate this.
--
Ticket URL: <https://trac.macports.org/ticket/60818#comment:11>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list