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:
> 
>  - A bug in libguile (e.g. offset by one error, corrupted lists, null
>    pointer access)
>  
>  - A violation of the Scheme specification (e.g. using set-car! on a
>    constant literal)
> 
> 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
-- 
t

Attachment: signature.asc
Description: PGP signature

Reply via email to