Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #15987

Change in SIGTERM behaviour in bash 4.3 when using readline

Show all headers | View raw

Hi there,

A question on Unix & Linux Stack Exchange[0] brought up the question of SIGTERM 
terminating interactive bash shells. This surprised me, and after bisecting I 
narrowed it down to commit ac50fbac ("Bash-4.3 distribution sources and 
documentation").

Going through the commit I see a significant number of changes, like the 
addition of setting/checking the sigterm_received atomic in a number of places, 
and the special handling of some signals (including SIGTERM) as part of 
deciding whether to call rl_signal_event_hook.

It seems this behaviour is related to readline, because it goes away if I run 
with --noediting.

Before I spend the time to look through the code to work out exactly which part 
of ac50fbac results in this behaviour, since it's fairly substantial, I want to 
double check -- was this an intentional change or not? I can't really tell from 
CHANGES or NEWS: they mention some of the compile-time options around SIGTERM 
and rl_signal_event_hook, but I can't really tell the intent when it comes to 
this behaviour in particular. Certainly it came as a surprise to me, at least.

Thanks,

Chris

0: https://unix.stackexchange.com/q/571123/10762

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Change in SIGTERM behaviour in bash 4.3 when using readline Chris Down <chris@chrisdown.name> - 2020-03-04 18:18 +0000

csiph-web