Re: write() not retried after EINTR in printf and echo

On 12/18/18 8:06 PM, Bize Ma wrote: > In here: > https://lists.gnu.org/archive/html/bug-bash/2018-01/msg00032.html > > > You promised: > > The > next version of bash will install its SIGWINCH handler with SA_RESTART. > > > > Yet: > Still a bug in bash version 5 And yet, when you look at the

memory leak in bash only during boot up in Bash-3.2.48

create a shell script from below given code. name it testing.sh. #!/bin/bash logger "Started testing" while(true); do while (true); do ls > /dev/null ; done done Steps. # chmod 755 /root/testing.sh modify any /etc/init.d/"service" file add "/root/testing.sh" inside the start case. "se

Memory continusely increase

Hi all, I did a test about run a bash scriplt never quit,but met a memory usage issue that cause used memory continuous increase. This issue was present in bash-3.2.x, bash-4.0.x, bash-4.1.x, bash-4.2.x, bash-4.3.x. However, This issue was disappeared in bash-4.4.0, I can't trace which patch fixed

Memory continuesly increase

Hi all,I did a test about run a bash scriplt never quit,but met a memory usage issue that cause used memory continuous increase.This issue was present in bash-3.2.x, bash-4.0.x, bash-4.1.x, bash-4.2.x, bash-4.3.x. However, This issue was disappeared in bash-4.4.0, I can't trace which patch fixed th

Re: Memory continusely increase

+ Adding Abhishek Hi Chen and Abhishek, it seems you might work on the same team since you sent the exact same bug report: - http://lists.gnu.org/archive/html/bug-bash/2018-12/msg00059.html - http://lists.gnu.org/archive/html/bug-bash/2018-12/msg00058.html - http://lists.gnu.org/archive/html/bug-

Re: Bash build issues in `devel' branch due to -Werror compiler flag

On Mon, Dec 17, 2018 at 6:31 AM Chet Ramey wrote: (...) > Good. This is the kind of feedback I want from enabling this option during > the pre-release period. Thanks for taking the time. Thank you! Bash `devel' builds fine for me now.

Re: write() not retried after EINTR in printf and echo

Chet Ramey () wrote: > And yet, when you look at the source, the signal handlers are installed > with SA_RESTART. For example, > > # if defined (SIGWINCH) > act.sa_flags = (sig == SIGWINCH) ? SA_RESTART : 0; > # else > act.sa_flags = 0; > # endif /* SIGWINCH */ > > in lib/readline/signals

Error on arithmetic evaluation of `~0`.

This is the third time I am reporting this issue. This fails: var=(hello); echo "${var[~0]}" syntax error: operand expected ... While this works: var=(hello); echo "${var[ ~0]}" hello It is also interesting that this fails: var=hello; echo "${var[ ~0]}" bash: var: bad array subscript Isn't `

Re: Memory continusely increase

Eduardo Bustamante 于2018年12月20日周四 上午1:58写道： > > + Adding Abhishek > On Wed, Dec 19, 2018 at 6:45 AM jake wrote: > > > > Hi all, > > > > I did a test about run a bash scriplt never quit,but met a memory usage > > issue that cause used memory continuous increase. > > This issue was present in bash

Terminating background bash kills the parent?

Open a new terminal like xterm, change prompt to something like: PS1=' $SHLVL $ ' Start a couple of bash subshells: 1 $ bash 2 $ bash 3 $ echo $$ 9371 Suspend the last one: 3 $ suspend [1]+ Stopped bash 2 $ echo $$ 9313 2 $ Make the susp