Re: macOS status
"Kirill A. Korinsky" <[email protected]>
| Newsgroups | gmane.lisp.gcl.devel |
|---|---|
| Message-ID | <[email protected]> |
Hello, > On 24. Dec 2023, at 15:37, Camm Maguire <[email protected]> wrote: > >> >> Anyway, failed on build; crash happened inside siLheap_report which is called by the first (init-system) at ./raw_pre_gcl > > Is this heap report issue the same as your segmentation catcher signal > unblocking issue and limited to arm64 alone? yes, removing segmentation catcher signal allows to see it. Without it, it simple fails with error in console without any trace. FYI: it isn't arm64 build, because configure script doesn't support it. I use so-called Rosetta to run x86_64 binary on arm64 which usually works quite well. -- wbr, Kirill
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE3/KLNtcfWfLw7JxqmNjZhndZIm4FAmWIQuYACgkQmNjZhndZ Im6z9g//ZXtjMAPj3MdWy8mBYi+XjBl7iPMeeohhzFPU9apj38b0UIAxDSGVu9N4 c76HQvtv7R3ou5c927fP1vM6LEUUuRPE1sqK80eLWtcadV5Imi/6hkO5Y9H6SSiX jQI2ni3tsCZUaKBUOnWr8+DtcNBya2lapLyrfQmZckRtPA/HPWyQjVl2BaWcyCro GZ2SZ3xJJugI3pVpJHD/a2XQ241YKVh9GvVhUGqW/sDctrLy+7Ov306hZFXViQJ5 ciK88R9NTVotJpPM7peQ0sRXTwYdvxlfEDDd5TsD8vqGTwN7Zk+gznCc9UEYtOwW KB3zjP+oht53MAbFgBI4abWnQkdGSGPCrc4NGLR1+aqXTSl360MFJ5gpzgtn6B0W 6WC+IIw1vKEwBGgZA+DasISYo8FiD0aOVB0v1ZaFd1vBISgPVGW98TgeTMGGX/uS 7Oc8AB19JwW8JO7C2COyi0lm3eULX5SonrQLp+WAiJ49nYnfx3AdgoHQ2jW9BKDO AFSwvn3Dzd1F0dQKZddd8uXg1SlD93keL3jDjJIOxTi/1B0AQLfnnE5Yi0lF9dN5 EDwJjOhOqrmXGSgmrOvL5hndAOXB0OMVkQBOqa/40xDkLV6eno5Af2RY/Zln4VEU uuWUmjPV6Joy5RiyBrKd9s7mZb9H/3ZW/yYf0/1UqxGx8l5LjME= =GxJW -----END PGP SIGNATURE-----