Re: bash support for XDG Base Directory spec (~/.config/bash/)

2021-11-02 Thread Siteshwar Vashisht
On Fri, May 7, 2021 at 11:48 AM Allison Karlitskaya < allison.karlitsk...@redhat.com> wrote: > hello, > > Please consider these two patches for inclusion in bash to support > storing shell initialisation files (profile, bashrc) in a subdirectory > of ~/.config/ as most programs do these days. > >

read builtin goes into uninterruptible loop if input only contains zeros

2017-07-28 Thread Siteshwar Vashisht
2017 x86_64 x86_64 x86_64 GNU/Linux Machine Type: x86_64-unknown-linux-gnu Bash Version: 4.4 Patch Level: 12 Release Status: release Description: read builtin goes into uninterruptible loop if input comes from /dev/zero. Repeat-By: read -N 1 _ < /dev/zero Fi

Re: read builtin goes into uninterruptible loop if input only contains zeros

2017-07-28 Thread Siteshwar Vashisht
Modified the patch to print warning only once when null byte is ignored. - Original Message - > From: "Siteshwar Vashisht" > To: bug-bash@gnu.org > Sent: Friday, July 28, 2017 3:59:15 PM > Subject: read builtin goes into uninterruptible loop if input on

Re: read builtin goes into uninterruptible loop if input only contains zeros

2017-07-30 Thread Siteshwar Vashisht
- Original Message - > From: "Chet Ramey" > To: "Siteshwar Vashisht" , bug-bash@gnu.org > Cc: "chet ramey" > Sent: Sunday, July 30, 2017 4:33:09 PM > Subject: Re: read builtin goes into uninterruptible loop if input only > contains zer

Cleanup compiler warnings

2017-07-30 Thread Siteshwar Vashisht
Hello, Attached patch cleans up compiler warnings about unused variables, functions etc. while compiling with '-Wall' option in gcc. -- -- Siteshwar Vashisht From 83394f684ab0b5451c351e37411e8cab3c4ed42a Mon Sep 17 00:00:00 2001 From: Siteshwar Vashisht Date: Sun, 30 Jul 2017 16:0

Integer overflow in command substitution

2017-11-16 Thread Siteshwar Vashisht
-linux-gnu Bash Version: 4.4 Patch Level: 12 Release Status: release Repeat-By: $ bash -c 'true $(yes )' bash: xrealloc: cannot allocate 18446744071562067968 bytes Fix: Attached patch fixes this issue. -- -- Siteshwar Vashisht From a91b113be8fca1a38b2b7f67

What should be the expected behavior for $_ ?

2018-04-03 Thread Siteshwar Vashisht
if a command gets executed in background ? [1] https://www.gnu.org/software/bash/manual/html_node/Special-Parameters.html#Special-Parameters -- -- Siteshwar Vashisht

Re: Bash patches format

2018-06-03 Thread Siteshwar Vashisht
ff, but quilt 3.0 > requires -p1 (see > https://lists.debian.org/debian-devel/2009/03/msg00368.html). > [1] https://src.fedoraproject.org/rpms/bash/blob/master/f/bash.spec#_125 -- -- Siteshwar Vashisht

Bash fails to exit if parent ssh process is killed during command search

2018-06-15 Thread Siteshwar Vashisht
9822 ?Ss 0:00 \_ sshd: situ [priv] 9825 ?S 0:00 \_ sshd: situ@pts/8 9834 pts/8Ss+0:00 \_ -bash 4. Kill the parent process of bash by executing: kill -hup 9825 5. Bash gets stuck in a loop and shows 100% cpu usage. Fix: See attached

Re: What should be the expected behavior for $_ ?

2019-11-25 Thread Siteshwar Vashisht
- Original Message - > From: "L A Walsh" > To: "chet ramey" > Cc: bug-bash@gnu.org, "Siteshwar Vashisht" > Sent: Wednesday, April 4, 2018 2:03:05 AM > Subject: Re: What should be the expected behavior for $_ ? > > > > Che

Race condition in handling SIGHUP

2016-04-27 Thread Siteshwar Vashisht
4 [7] http://git.savannah.gnu.org/cgit/bash.git/tree/general.c#n994 [8] http://git.savannah.gnu.org/cgit/bash.git/tree/sig.c#n524 -- Siteshwar Vashisht Software Engineer From 1ecc0ff050d74aef548677fb97b2113b0920c711 Mon Sep 17 00:00:00 2001 From: Siteshwar Vashisht Date: Mon, 25 Apr 2016 14:04

Race condition in handling SIGHUP

2016-04-27 Thread Siteshwar Vashisht
4 [7] http://git.savannah.gnu.org/cgit/bash.git/tree/general.c#n994 [8] http://git.savannah.gnu.org/cgit/bash.git/tree/sig.c#n524 -- -- From 1ecc0ff050d74aef548677fb97b2113b0920c711 Mon Sep 17 00:00:00 2001 From: Siteshwar Vashisht Date: Mon, 25 Apr 2016 14:04:10 +0530 Subject: [PATCH] Do

Re: Race condition in handling SIGHUP

2016-04-29 Thread Siteshwar Vashisht
- Original Message - > From: "Chet Ramey" > To: "Siteshwar Vashisht" , bug-bash@gnu.org > Cc: dkas...@redhat.com, "chet ramey" > Sent: Thursday, April 28, 2016 6:19:17 PM > Subject: Re: Race condition in handling SIGHUP > > On 4/27

Re: Autocompletion problems with nounset and arrays

2016-05-19 Thread Siteshwar Vashisht
global_nounset; if (wl) nounset should be turned off for all completions and not just for one specific case. > > Chet > > -- > ``The lyf so short, the craft so long to lerne.'' - Chaucer >``Ars longa, vita brevis'' - Hippocrates > Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/ > -- -- Siteshwar Vashisht

Re: bug in [ -f file ] test

2016-07-28 Thread Siteshwar Vashisht
ps://bugzilla.redhat.com/show_bug.cgi?id=1329691#c0 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1333764 -- -- Siteshwar Vashisht

Bash crashes while handling very long string in parameter expansion

2016-08-09 Thread Siteshwar Vashisht
ot; OUT=`${CMD} 2>&1` echo "${CMD} completed..." echo "Command Output : ${CMD} ${OUT}" > /dev/null exit 1 Execute the script : /usr/local/bin/bash test.sh data1g Result: Bash crashes with segmentation fault -- -- Siteshwar Vashisht

Re: Bash crashes while handling very long string in parameter expansion

2016-08-10 Thread Siteshwar Vashisht
- Original Message - > From: "Chet Ramey" > To: "Siteshwar Vashisht" , bug-bash@gnu.org > Cc: "chet ramey" > Sent: Tuesday, August 9, 2016 7:43:54 PM > Subject: Re: Bash crashes while handling very long string in parameter > expan

Bash leaks heredoc fd to child processes

2017-01-17 Thread Siteshwar Vashisht
Hello, Bash leaks heredoc fd to child processes if heredoc string contains command substitution. Reproducer code : $ cat test.sh #!/bin/bash cat <From 6b7970ee787cf042182f8f93bf25c6e6453a8aef Mon Sep 17 00:00:00 2001 From: Siteshwar Vashisht Date: Tue, 17 Jan 2017 10:28:34 +0100 Subj

Re: Bash leaks heredoc fd to child processes

2017-01-17 Thread Siteshwar Vashisht
- Original Message - > From: "John McKown" > To: "Chester Ramey" > Cc: bug-bash@gnu.org, "Siteshwar Vashisht" > Sent: Tuesday, January 17, 2017 5:14:44 PM > Subject: Re: Bash leaks heredoc fd to child processes > > ​Probabl

Re: Bash leaks heredoc fd to child processes

2017-01-17 Thread Siteshwar Vashisht
- Original Message - > From: "Chet Ramey" > To: "Siteshwar Vashisht" , bug-bash@gnu.org > Cc: "chet ramey" > Sent: Tuesday, January 17, 2017 7:42:07 PM > Subject: Re: Bash leaks heredoc fd to child processes > > Thanks for the report

read() may fail due to nonblocking stdin

2017-01-22 Thread Siteshwar Vashisht
t $ ./test.sh read failed: Resource temporarily unavailable cat: -: Resource temporarily unavailable Attached patch sets standard file descriptors to blocking before child process starts. -- -- Siteshwar Vashisht From f4fd3c17cb15f87fc8733b44bd477e32ff2d002a Mon Sep 17 00:00:00 2001 From: Siteshwar

Re: read() may fail due to nonblocking stdin

2017-01-24 Thread Siteshwar Vashisht
- Original Message - > From: "Chet Ramey" > To: "Siteshwar Vashisht" , bug-bash@gnu.org > Cc: "chet ramey" > Sent: Monday, January 23, 2017 8:01:38 PM > Subject: Re: read() may fail due to nonblocking stdin > > Something like this,

Make syslog history configurable

2017-01-25 Thread Siteshwar Vashisht
Hello, Bash history is logged to syslog if SYSLOG_HISTORY macro is defined in config-top.h. There is no option to enable/disable it at runtime. I am adding a shell option 'syshist' that can be used to configure logging bash history to syslog at runtime. -- -- Siteshwar Vas

Re: Make syslog history configurable

2017-01-25 Thread Siteshwar Vashisht
- Original Message - > From: "Siteshwar Vashisht" > To: bug-bash@gnu.org > Sent: Wednesday, January 25, 2017 1:39:12 PM > Subject: Make syslog history configurable > > Hello, > > Bash history is logged to syslog if SYSLOG_HISTORY macro is defined in

'history -n' should re-read history file if history is cleared

2017-04-17 Thread Siteshwar Vashisht
Reproducer steps : > PROMPT_COMMAND="history -a; history -c; history -n" > history Actual output : 2 history Expected output: All the older history items from bash history file should be re-read. I am providing a test patch that resolves this issue. -- -- Siteshwar Vas

Re: 'history -n' should re-read history file if history is cleared

2017-04-20 Thread Siteshwar Vashisht
- Original Message - > From: "Chet Ramey" > To: "Siteshwar Vashisht" , bug-bash@gnu.org > Cc: "chet ramey" > Sent: Tuesday, April 18, 2017 5:36:05 PM > Subject: Re: 'history -n' should re-read history file if history is cleared

test builtin does not check for nanoseconds while comparing timestamps

2017-06-02 Thread Siteshwar Vashisht
config.h. Repeat-By: while true; do touch a; sleep 0.1; touch b; stat a b|grep Modify; [ b -nt a ] && echo test_cmd_ok || echo test_cmd_failed; echo; done Fix: Attached patch fixes this issue. -- -- Siteshwar Vashisht From 2648afeb4e2bae4e250700c8fb37e2aa64c82b11