Re: Handling page faults in syscalls

--Apple-Mail=_51598C51-28FC-4D7D-889A-46C019B9945A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



> Am 23.12.2025 um 10:41 schrieb [email protected]:

> I think I think of it like, the responsibility for fixing this kind of =
problem is on the packager, and it would be much better to fail noisily =
so it can be caught earlier by the people who should be fixing it.

On Linux external libraries are usually provided by the distribution. I =
think a concern is that we don't want so spam the user if e.g. the 32 =
bit LDAP library fails to load. For things like GL/Vulkan/d3d there is =
usually a more obvious message if the application does try to make use =
of it rather than just accidentally linking to ddraw.

That said, I am not the one who wrote the syscall infrastructure, so I =
am just guessing here.=

--Apple-Mail=_51598C51-28FC-4D7D-889A-46C019B9945A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEQxb0tqoFWyeVMl1sPRO8yFRPGiIFAmlPoJQACgkQPRO8yFRP
GiJVoQ/+M9/SvwA2oiNhjavlH/ub/MzUjZc0I2+jr3SNW5IDSUEQPswK8Z8x7yQT
erfwx930DYu059jn8SZI/oPlXYFgxK+rDXWJ3lt0bzB9NSFKUfEMlWr9HcBqQafJ
yRj0Ukf8Qa0M2JuOuWzB6Rz03chdFrDwfvAOOoypXedwGCdb2E0qtMy0bp2hSKXk
8ppDsBMVme0tbPZh2X8WSzb6eWiLDwg3MXgf3BUn5TtcPSaN+sEZYCJguOvek9Oh
/xDs8CDv2MhL9u0W3k7iN0JSbZmNDONsj6SfBXCXbvBRvjH9hkZjrzZ/yzIZtVgP
IrNs2+QnQsAqH7k2Gu7lc4UP8Ozc6rnDuZiumY0ecOA1pSbicjhGMeKh+7FQMtRt
4HYLst60FLoLugMhG9DjiFRIVc4fsPEMELsPv6k52gM826bsgq8DO69M6M86I1gn
9qtV7099foLEp+y2tKLyjU/eoT0Q4QRd+tP6EnjxYtFFpZQj+SxbGJJ5hXna1VCq
EV5mUDlVz+T5/y/3I317DOLuxdI2AS7fhfT9gnpi+QizrkMsmD/MJUMJqB3LUJms
+YDx7uMtnmAn0VPHWrn2aMbaAa73hpmyljp3QSL2T0cMqbn7HjF8GV9jppM3zTLs
csKXhJ6ygkn2J744aeJVCD4hEDbSkMkumBgIKuiQC7Mn6ID6C2s=
=O/fO
-----END PGP SIGNATURE-----

--Apple-Mail=_51598C51-28FC-4D7D-889A-46C019B9945A--