GNU bug report logs - #58440
27.2; Exit Code on SIGINT is Zero, But shouldn't Be

Previous Next

Full log

Message #58 received at 58440 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Mattias Engdegård <mattias.engdegard <at> gmail.com>,
 mwelinder <at> gmail.com, 58440 <at> debbugs.gnu.org
Subject: Re: bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be
Date: Thu, 13 Oct 2022 21:03:19 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

>> > I'm proposing that we exit on a non-zero value if and when we decide to
>> > exit after a SIGKILL.
>> 
>> Done!
>
> That was AFAIU a proposal for discussion, not a request to make the
> change right there and then.

I think that was a joke.  😀

Eli Zaretskii <eliz <at> gnu.org> writes:

> How do you see that we exit with zero status now?  I mean, not by
> looking what the shell says, but by tracing the code which handles
> SIGINT?  I'd like to see what code we are talking about before making
> up my mind about the change you propose.

I haven't been able to follow the interrupt handling logic (after
looking at it for a couple minutes), so I don't know.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.