Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1063149

Bug#990264: Bug#990265: Bug#990264: Bug#990265: mksh: output error is not checked for some builtins when stdout is closed

From Thorsten Glaser <tg@mirbsd.de>
Newsgroups linux.debian.bugs.dist
Subject Bug#990264: Bug#990265: Bug#990264: Bug#990265: mksh: output error is not checked for some builtins when stdout is closed
Date 2021-06-27 19:40 +0200
Message-ID <CuGVb-6br-1@gated-at.bofh.it> (permalink)
References (2 earlier) <Cty3E-3IB-7@gated-at.bofh.it> <Ctujn-1ph-1@gated-at.bofh.it> <CuFFL-5x4-5@gated-at.bofh.it> <Ctu9I-1m3-5@gated-at.bofh.it> <CuFFL-5x4-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Anuradha Weeraman dixit:

>"At program start-up, three streams shall be predefined and already open:
>stdin (standard input, for conventional input) for reading, stdout
>(standard output, for conventional output) for writing, and stderr
>(standard error, for diagnostic output) for writing." [1]

Isn’t this what I already found in the online docs?

>[1] - https://austingroupbugs.net/view.php?id=1347#c5161

Ah, a clarification then. Very good! Thanks for spotting this.

>Also, some more elaboration by POSIX on unspecified behavior if the
>standard streams are not open for reading and writing:
>
>"If a standard utility or a conforming application is executed with file
>descriptor 0 not open for reading or with file descriptor 1 or 2 not
>open for writing, the environment in which the utility or application
>is executed shall be deemed non-conforming, and consequently the utility
>or application might not behave as described in this standard." [2]

Ah, good to know; this explicitly confirms that this is not a bug.
I should have looked there.

bye,
//mirabilos
-- 
Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht damit
gerechnet, darum bin ich blutverschmiert… wer konnte ahnen, daß SIE so
reagier’n… gestern Nacht ist mein IRC-Netzwerk explodiert~~~
	(as of 2021-06-15 The MirOS Project temporarily reconvenes on OFTC)

Back to linux.debian.bugs.dist | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#990265: mksh: output error is not checked for some builtins Vincent Lefevre <vincent@vinc17.net> - 2021-06-24 12:00 +0200
  Bug#990264: Bug#990265: mksh: output error is not checked for some builtins when stdout is closed Thorsten Glaser <tg@mirbsd.de> - 2021-06-24 16:00 +0200
    Bug#990264: Bug#990265: mksh: output error is not checked for some builtins when stdout is closed Vincent Lefevre <vincent@vinc17.net> - 2021-06-24 16:30 +0200
      Bug#990264: Bug#990265: mksh: output error is not checked for some builtins when stdout is closed Vincent Lefevre <vincent@vinc17.net> - 2021-06-24 16:40 +0200
      Bug#990264: Bug#990265: mksh: output error is not checked for some builtins when stdout is closed Thorsten Glaser <tg@mirbsd.de> - 2021-06-24 17:20 +0200
    Bug#990264: Bug#990265: mksh: output error is not checked for some builtins when stdout is closed Anuradha Weeraman <anuradha@debian.org> - 2021-06-27 18:20 +0200
      Bug#990264: Bug#990265: Bug#990264: Bug#990265: mksh: output error is not checked for some builtins when stdout is closed Thorsten Glaser <tg@mirbsd.de> - 2021-06-27 19:40 +0200
      Bug#990264: Bug#990265: mksh: output error is not checked for some builtins when stdout is closed Vincent Lefevre <vincent@vinc17.net> - 2021-06-27 23:30 +0200
        Bug#990264: Bug#990265: mksh: output error is not checked for some builtins when stdout is closed Thorsten Glaser <tg@mirbsd.de> - 2021-06-27 23:50 +0200
  Bug#990265: utilities and write errors mirabilos <tg+ml@mirbsd.org> - 2021-06-30 03:00 +0200
    Bug#990265: utilities and write errors Vincent Lefevre <vincent-opgr@vinc17.net> - 2021-06-30 03:30 +0200
      Bug#990265: utilities and write errors Thorsten Glaser <tg@mirbsd.de> - 2021-06-30 04:10 +0200

csiph-web