bug#79483: Segmentation fault: set-car! in compiled code

--OliiGvXCMsiQcXbF
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 16, 2026 at 08:56:33AM -0500, Olivier Dion wrote:

[...]

> The problem is that we don't know if the memory access is:
>=20
>  - A bug in libguile (e.g. offset by one error, corrupted lists, null
>    pointer access)
> =20
>  - A violation of the Scheme specification (e.g. using set-car! on a
>    constant literal)
>=20
> And this is where the difficulty arise.  What I think is necessary is to
> fork the faulty thread in the signal handler and pause.  The child can
> then serialize some of the information needed for crash reporting,
> e.g. PID, TID, siginfo fields. Then, it execve a crash handler program.

[...]

I understand it would be nasty, if at all possible. Perhaps not worth
the complexity.

Cheers
--=20
t

--OliiGvXCMsiQcXbF
Content-Type: application/pgp-signature; name="signature.asc"

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

iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCaZNSPgAKCRAFyCz1etHa
RvyaAJ9xzqyREQJv87hGkZhgKbO3Qya1DQCeJYrqzkNbasgdAu/b1WCHn/lFhoo=
=afdz
-----END PGP SIGNATURE-----

--OliiGvXCMsiQcXbF--