On 7/22/19 1:56 PM, k...@munnari.oz.au wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: netbsd
> Compiler: gcc
> Compilation CFLAGS: -O2 -D_FORTIFY_SOURCE=2 -I/usr/include -Wno-parentheses
> -Wno-format-security
> uname output: NetBSD jinx.noi.kr
2019-07-22 14:55:05 -0500, Eric Blake:
[...]
> > Even if POSIX didn't mandate
> >
> > printf -- -%s x
> >
> > to output -x, I'd say it would be a bug in the POSIX
> > specification (it looks like it is).
>
> POSIX _does_ mandate 'printf -- -%s x' to output exactly '-x', by virtue
> of the fact t
On 7/22/19 2:48 PM, Stephane Chazelas wrote:
> 2019-07-23 00:56:59 +0700, k...@munnari.oz.au:
> [...]
>> POSIX specifies that printf(1) has no options, and by not
>> specifying that it is intended to comply with XBD 12.2 effectivly
>> says that it is not. That is, in printf, the fi
On 7/22/19 12:56 PM, k...@munnari.oz.au wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: netbsd
> Compiler: gcc
> Compilation CFLAGS: -O2 -D_FORTIFY_SOURCE=2 -I/usr/include -Wno-parentheses
> -Wno-format-security
> uname output: NetBSD jinx.noi.k
2019-07-23 00:56:59 +0700, k...@munnari.oz.au:
[...]
> POSIX specifies that printf(1) has no options, and by not
> specifying that it is intended to comply with XBD 12.2 effectivly
> says that it is not. That is, in printf, the first arg is
> always the format string, what
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: netbsd
Compiler: gcc
Compilation CFLAGS: -O2 -D_FORTIFY_SOURCE=2 -I/usr/include -Wno-parentheses
-Wno-format-security
uname output: NetBSD jinx.noi.kre.to 8.99.30 NetBSD 8.99.30 (1.1-20190114) #9:
Mon Jan 14 1
On 7/20/19 2:05 PM, Bonjour Abracadraba wrote:
> Bash Version: 5.0
> Patch Level: 3
> Release Status: release
>
> Description:
> Bash 2.04 through 5.0 crash when trying to write to a closed socket.
> It is expected for bash to give an user error, but it exits instead.
This seems like user
