Hi,
Sending rapid SIGINTs from another shell quickly results in a SEGFAULT of the
bash instance receiving them. Steps to reproduce:
* Open up a shell SHELL_1 and record its pid, e.g. "echo $$"
* Launch another shell and send rapid SIGINTs: while true ; do kill -INT
OTHER_PID; done
SHELL_1 quick
Hi,
when compiling bash with a plain
mkdir build; cd build; ../configure && make
the login shell detection (leading dash: -bash) is apparently broken - at
least, ~/.bashrc is not sourced.
This happens in all tested versions, from 4.4 until the latest release 5.2.15.
Interestingly, using distrib
Am 16.01.23 um 18:26 schrieb Chet Ramey:
The fix is to add enough state machinery to detect this situation and
behave in a way that can satisfy both the standard and the later
interpretation, while being careful not to undo this work later. This is
obviously not how bash worked in the past.
Am 13.01.23 um 03:02 schrieb Robert Elz:
Date:Fri, 13 Jan 2023 00:34:02 +0100
From:Tycho Kirchner
Message-ID: <7d59c17d-792e-0ac7-fd86-b3b2e7d4b...@mail.de>
| we found quite some inconsistency and weirdness
| in the handling of SIGINT's d
Hi,
we found quite some inconsistency and weirdness in the handling of SIGINT's
during async function calls and were wondering, whether those are expected. All
calls were executed from a script with jobcontrol turned off (set +m) while
pressing Ctrl+C shortly afterwards. In summary:
The main IN
Dear bash-maintainers,
Description:
When another instance of bash is called *within the .bashrc* using the
exec-builtin within a tty (e.g. Ctrl+Alt+F1) the following error
occurs:
initialize_job_control: no job control in background: Bad file
descriptor
On the next keypress
Am 13.04.19 um 21:19 schrieb Chet Ramey:
On 3/28/19 8:01 AM, Tycho Kirchner wrote:
Dear bash-maintainers,
the *interactive* bash leaks (pipe-)file-descriptors when fast interrupts
(SIGINT) occur. The bug occurs on all bash-versions tested (see below),
including 5.0.2(1)-release.
I don'
Dear bash-maintainers,
the *interactive* bash leaks (pipe-)file-descriptors when fast
interrupts (SIGINT) occur. The bug occurs on all bash-versions tested
(see below), including 5.0.2(1)-release.
The bug is most easily reproduced using two terminals.
# Terminal one:
# Setup a PROMPT_COMMAND
