kc3-lang/gnulib/doc/posix-functions/stdout.texi

• Show log

  Commit

• Hash : be8a5aef
  Author :
  Date : 2024-11-06T12:32:27
  

  Document xstdopen vs *-safer better
  

Download

• doc/posix-functions/stdout.texi

• @node stdout
  @subsection @code{stdout}
  @findex stdout
  
  POSIX specification:@* @url{https://pubs.opengroup.org/onlinepubs/9799919799/functions/stdout.html}
  
  Gnulib module: ---
  
  Portability problems fixed by Gnulib:
  @itemize
  @end itemize
  
  Portability problems not fixed by Gnulib:
  @itemize
  @item
  stdout is created in 32-bit mode instead of 64-bit mode: Cygwin 1.5.x.
  One workaround is to use @code{freopen(NULL, "w", stdout)} on Cygwin 1.5.21
  or newer.
  @mindex ftello
  Another is to use the gnulib @code{ftello} module and do
  @code{ftello(stdout)}.
  @item
  POSIX states that a setuid application can guarantee that fd 1 is
  open, but some systems guarantee this even for non-setuid programs.
  If an application is executed with fd 1 closed, use of @code{stdout}
  can affect an unrelated file that happened to be assigned to fd 1.
  The gnulib @code{xstdopen} or the *-safer modules may be used to
  guarantee that fd 1 stays
  reserved for @code{stdout}.
  @end itemize
  

Download