Re: Bad leaks file fd to child processes

2022-11-28 Thread Alexey via Bug reports for the GNU Bourne Again SHell
On 2022-11-28 14:20, Koichi Murase wrote: 2022年11月28日(月) 19:06 Alexey via Bug reports for the GNU Bourne Again SHell : But we use the fact tat bash doesn't close FD for example to preliminary open log file for utility that we will `exec' later. Unfortunately bash doesn't provide any fcntl

Re: Bad leaks file fd to child processes

2022-11-28 Thread Alexey via Bug reports for the GNU Bourne Again SHell
On 2022-11-26 14:05, "凋叶棕" via Bug reports for the GNU Bourne Again SHell wrote: Hello, I find that the file descriptor leaks when I execute the command pvs in bash 5.2, The abnormal scenario is similar to the bug which reported by

Re: [bash 4] 'test -v 1' is never true

2022-11-27 Thread Alexey via Bug reports for the GNU Bourne Again SHell
On 2022-11-26 21:45, Alejandro Colomar wrote: That was my gut; thanks! I'll workaround with $#. I could suggest you to use for clarity another construction: [[ ${1+isset} ]] || echo "not set" Here "isset" is just for readability. You could place any other string literal there. Regards,

Re: >&"$var" broken in declare -f and exported functions

2022-06-06 Thread Alexey via Bug reports for the GNU Bourne Again SHell
On 2022-06-06 05:31, Namikaze Minato wrote: On Fri, 3 Jun 2022 at 23:24, Alexey wrote: As I can see, problem exist only if we quote "$foo". Without quotes everything looks fine. Hello Alexey. Thank you for the workaround of removing the quotes. And sorry for my being late to answer.

Re: >&"$var" broken in declare -f and exported functions

2022-06-03 Thread Alexey via Bug reports for the GNU Bourne Again SHell
On 2022-06-03 19:18, Namikaze Minato wrote: Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: x86_64-pc-linux-gnu-gcc Compilation CFLAGS: -march=native -O2 uname output: Linux ns3012044.ip-37-187-96.eu 4.9.120--std-ipv6-64 #327490 SMP

Re: bash 5.1 heredoc pipes problematic, shopt needed

2022-04-28 Thread Alexey via Bug reports for the GNU Bourne Again SHell
Hello. On 2022-04-28 20:56, Greg Wooledge wrote: Second, none of your examples work with arbitrary filenames, which may contain newline characters. The solution to that is to use find -print0 and to read the NUL-delimited stream in the shell. I want to assure you (and others) that my point

Re: bash 5.1 heredoc pipes problematic, shopt needed

2022-04-28 Thread Alexey via Bug reports for the GNU Bourne Again SHell
On 2022-04-26 01:05, Alexey via Bug reports for the GNU Bourne Again SHell wrote: On 2022-04-26 00:54, Chet Ramey wrote: On 4/25/22 4:33 PM, Alexey wrote: My key point that we have two choices for future:  - make read from pipe faster, or You mean the read builtin, right? I already

Re: bash 5.1 heredoc pipes problematic, shopt needed

2022-04-25 Thread Alexey via Bug reports for the GNU Bourne Again SHell
On 2022-04-26 00:54, Chet Ramey wrote: On 4/25/22 4:33 PM, Alexey wrote: My key point that we have two choices for future:  - make read from pipe faster, or You mean the read builtin, right? I already explained those semantics.  - provide options for force here-string to use temp files.

Re: bash 5.1 heredoc pipes problematic, shopt needed

2022-04-25 Thread Alexey via Bug reports for the GNU Bourne Again SHell
On 2022-04-25 23:55, Chet Ramey wrote: On 4/25/22 1:03 PM, Alexey wrote: There is one more problem with pipes — they are extremely slow. It's not pipes per se -- it's the semantics of the shell `read' builtin and standard input. Profiling or a system call tracer would have provided

Re: bash 5.1 heredoc pipes problematic, shopt needed

2022-04-25 Thread Alexey via Bug reports for the GNU Bourne Again SHell
On 2022-04-25 21:03, Alexey wrote: On 2022-04-25 17:14, Chet Ramey wrote: On 4/24/22 4:26 PM, Alexey via Bug reports for the GNU Bourne Again SHell wrote: My pipe size is 4kb, but...   ulimit -p   8   { file /proc/self/fd/0; } <<<"$(dd if=/dev/urandom bs=1 count=$((4096*16

Re: bash 5.1 heredoc pipes problematic, shopt needed

2022-04-25 Thread Alexey via Bug reports for the GNU Bourne Again SHell
On 2022-04-25 17:14, Chet Ramey wrote: On 4/24/22 4:26 PM, Alexey via Bug reports for the GNU Bourne Again SHell wrote: My pipe size is 4kb, but...   ulimit -p   8   { file /proc/self/fd/0; } <<<"$(dd if=/dev/urandom bs=1 count=$((4096*16)))"   /proc/self/fd/0: sy

Re: bash 5.1 heredoc pipes problematic, shopt needed

2022-04-24 Thread Alexey via Bug reports for the GNU Bourne Again SHell
On 2022-04-25 01:02, Greg Wooledge wrote: On Mon, Apr 25, 2022 at 12:26:46AM +0400, Alexey via Bug reports for the GNU Bourne Again SHell wrote: My pipe size is 4kb, but... ulimit -p 8 $ ulimit -a [...] pipe size(512 bytes, -p) 8 Always check the units. I have checked

Re: bash 5.1 heredoc pipes problematic, shopt needed

2022-04-24 Thread Alexey via Bug reports for the GNU Bourne Again SHell
On 2022-04-22 17:51, Sam Liddicott wrote: Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -g -O2 -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat

Re: for loop over parameter expansion of array can miss resulted empty list

2022-03-21 Thread Alexey via Bug reports for the GNU Bourne Again SHell
I can add one more example, which change array size while it's not expected behavior: x=("/"); y=("${x[@]%/}"); echo "x size: ${#x[@]}, y size: ${#y[@]}" Goal of this example show that it is not only for loop issue.

Re: for loop over parameter expansion of array can miss resulted empty list

2022-03-21 Thread Alexey via Bug reports for the GNU Bourne Again SHell
nullglob is not applicable in this situation, because no 'Pathname Expansion' is occur. On 2022-03-21 14:40, Alex fxmbsw7 Ratchev wrote: i solve this by shopt -s nullglob On Sun, Mar 20, 2022, 22:07 Alexey via Bug reports for the GNU Bourne Again SHell wrote: Hello. Machine: x86_64

for loop over parameter expansion of array can miss resulted empty list

2022-03-20 Thread Alexey via Bug reports for the GNU Bourne Again SHell
Hello. Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall uname output: Linux alex 5.16.0-3-amd64 #1 SMP PREEMPT Debian 5.16.11-1 (2022-02-25) x86_64 GNU/Linux Machine Type: x86_64-pc-linux-gnu Bash Version: