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

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

> On 23.06.2025 00:43, [email protected] wrote:
>> 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?
>
> The behaviour you are describing is the default for all Unix processes 
> running in terminals. It's not the duty of SBCL to document OS defaults.
>

It is the behavior, but it does not have to be.  Is it
useful behavior or does it serve no purpose?

> Speaking in another way: is the behaviour you describe documented 
> anywhere for Python, Ruby, Perl, Erlang, and so on? I'm asking because 
> the Unix python/irb/perl/erl programs react in the very same way - 
> quitting and optionally producing core dumps.
>

I do not know about how those programs behave, but it is
beside the point of my question.

> Or in yet another way: where does the man page for the Unix cat binary 
> mention this? Because hitting Ctrl+4 on a running cat process does the same.
>

That ‘cat’ does is not significant as it is not a program
that users expect to interact with for long period without
dying unexpectedly.  Also, ‘cat’ might well want to
recognize a quit signal.  Does it serve a lisp to recognize
the quit signal and if so what purpose does it serve?  And
if not, can it be changed so that it intercepts and ignores
a quit signal (as many other programs do)?

-- 
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