Re: SBCL 2.3.11: Core dump after typing Control-4

Michał "phoe" Herda <[email protected]> writes:

> On 22.06.2025 23:24, [email protected] wrote:
>> SBCL users probably want to know
>>     - about this behavior
>>     - how to prevent it (besides "Do not press Ctrl-4.")
>
> This is like teaching users of SBCL that sending a SIGTERM to a process 
> is going to ask it to terminate. This is not SBCL's domain, but that of 
> the operating system that SBCL runs on.
>
> The SIGQUIT behaviour is defined by libc, see 
> https://www.gnu.org/software/libc/manual/html_node/Termination-Signals.html#index-SIGQUIT. 
> That's where the user should look to learn about the behaviour and how 
> to prevent it.
>

You are probably correct that this is how the maintainers
see this behavior (given how long SBCL has been in use).
There are many programs that can be run from a shell prompt
and not all of them take this approach.  Instead, they
intercept the signals and prevent them from causing a core
dump.

Is there an argument for continuing the current behavior,
that is, is it useful for SBCL to allow a user to interrupt
the lisp and dump core under some circumstances?  If so,
that could be documented.

-- 
The lyf so short, the craft so long to lerne.
- Geoffrey Chaucer, The Parliament of Birds.


_______________________________________________
Sbcl-help mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sbcl-help