[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be
From: |
Eli Zaretskii |
Subject: |
bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be |
Date: |
Wed, 12 Oct 2022 18:40:40 +0300 |
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: mwelinder@gmail.com, 58440@debbugs.gnu.org
> Date: Wed, 12 Oct 2022 16:41:00 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > What happens if you say
> >
> > ./src/emacs -Q && echo 'OK'
> >
> > does it say OK when you kill Emacs with SIGINT?
>
> Yes.
That's strange. So the next step is to attach a debugger to Emacs
before delivering SIGINT to it, and see why we don't exit with the
status of 1.
What I verified is that when I do
./src/emacs -Q -nw && echo 'OK'
and then type "kill -INT EMACS-PID" from another terminal, Emacs does
a keyboard quit (i.e. flashes the display and says "Quit" in the
echo-area), which is exactly as I expect. So in the -nw case, the
installed SIGINT handler is called and does what is expected.
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Morten Welinder, 2022/10/11
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Mattias Engdegård, 2022/10/12
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Lars Ingebrigtsen, 2022/10/12
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Lars Ingebrigtsen, 2022/10/12
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Mattias Engdegård, 2022/10/12
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Lars Ingebrigtsen, 2022/10/13
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Mattias Engdegård, 2022/10/13
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Lars Ingebrigtsen, 2022/10/13
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Eli Zaretskii, 2022/10/13
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Lars Ingebrigtsen, 2022/10/13
- bug#58440: 27.2; Exit Code on SIGINT is Zero, But shouldn't Be, Mattias Engdegård, 2022/10/13