Re: [PATCH] Unix domain socket filename redirection

2017-06-20 Thread Eduardo A . Bustamante López
On Tue, Jun 20, 2017 at 11:49:56AM -0400, tetsu...@scope-eye.net wrote: [...] > So implementing Unix Domain Sockets in the shell would give you the > ability to connect to existing services on the machine that use named > sockets for control (systemd, dbus, cups, etc.) or you could use the > featur

Re: Unexpected word splitting on $* when IFS is unset

2017-06-20 Thread Kevin Brodsky
On 20/06/2017 06:33, Eduardo A. Bustamante López wrote: > On Tue, Jun 20, 2017 at 01:13:07AM +0100, Kevin Brodsky wrote: > [...] >> When IFS is unset, unquoted $* undergoes word splitting as if IFS=' ', >> and not the expected IFS=$' \t\n'. All the other unquoted mass >> This is a regression that a

Re: [PATCH] Unix domain socket filename redirection

2017-06-20 Thread tetsujin
Unix Domain Sockets form the basis of a lot of the modern forms of Unix/Posix IPC. Compared to using TCP sockets for IPC, Unix Domain sockets allow you to control access to the resource with filesystem permissions, and identify the socket with a file path so you don't have to come up with a system

Re: bash sigabrt

2017-06-20 Thread Eduardo Bustamante
On Tue, Jun 20, 2017 at 9:12 AM, Rajaa, Mukuntha (Nokia - IN/Bangalore) wrote: > Hi, > > Bash-4.4.12(1) release occasionally coredumps. This was tested on mips64 > platform. Could you please confirm, is this a known bug or should I raise a > ticket for this ? This error means that bash's intern

bash sigabrt

2017-06-20 Thread Rajaa, Mukuntha (Nokia - IN/Bangalore)
Hi, Bash-4.4.12(1) release occasionally coredumps. This was tested on mips64 platform. Could you please confirm, is this a known bug or should I raise a ticket for this ? GNU gdb (GDB) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

AddressSanitizer: heap-use-after-free in readtok | PS1='$((b[x++}]))'

2017-06-20 Thread Eduardo A . Bustamante López
I don't know how to fix this. dualbus@debian:~/readline$ ASAN_OPTIONS=disable_coredump=0:unmap_shadow_on_exit=1:abort_on_error=1:detect_leaks=0 ~/src/gnu/bash-builds/devel-asan/bash bash-4.4$ PS1='$((b[x++}]))' bash: x++}: syntax error: invalid arithmetic operator (error token is "}") =

Re: Read builtin -e (readline) oddities

2017-06-20 Thread Chet Ramey
On 6/19/17 3:40 PM, Chet Ramey wrote: >> #3 >> Hit `C-x C-e' thrice. Also, the mapping of `\C-m' became `self-insert' >> instead >> of `accept-line'. > > `read -e' changes it because it's no longer the line delimiter. > >> dualbus@debian:~$ PATH= EDITOR=: read -e -d '' >> >> PATH= EDITOR

Re: Regression -- can't read input w/stderr redirect

2017-06-20 Thread Chet Ramey
On 6/20/17 8:25 AM, Greg Wooledge wrote: >> * "The man page of bash reads: '-d delim The first character of > [...] > > It's not in the man page. -d delim The first character of delim is used to terminate the input line, rather than newline. If delim is the

Re: Regression -- can't read input w/stderr redirect

2017-06-20 Thread Greg Wooledge
On Tue, Jun 20, 2017 at 02:01:51AM -0700, L A Walsh wrote: > * BASH???s ???read??? built-in supports '\0' as delimiter Yes, but not with that syntax. It uses the -d '' option, which is undocumented, but supported according to . >

Re: Regression -- can't read input w/stderr redirect

2017-06-20 Thread L A Walsh
Pierre Gaston wrote: Your response: you accuse him to lie to you. Huh? Are you daft? Just because I can't find something about bash corrupting input in google and ask where people have said this was said is accusing someone of lying? Sorry, but I'm looking for context to see exactly what