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

• Show log

  Commit

• Hash : 004f708a
  Author :
  Date : 2009-11-05T15:13:00
  

  freopen-safer: new module
  
  * modules/freopen-safer: New module.
  * m4/stdio-safer.m4 (gl_FREOPEN_SAFER): New macro.
  * lib/freopen-safer.c (freopen_safer): New file.
  * lib/stdio-safer.h (freopen_safer): New declaration.
  * lib/stdio--.h (freopen): New override.
  * MODULES.html.sh (File stream based Input/Output): Mention it.
  * doc/posix-functions/freopen.texi (freopen): Mention pitfalls and
  freopen-safer module.
  * doc/posix-functions/stderr.texi (stderr): Likewise.
  * doc/posix-functions/stdin.texi (stdin): Likewise.
  * doc/posix-functions/stdout.texi (stdout): Likewise.
  * modules/freopen-safer-tests: New test.
  * tests/test-reopen-safer.c: New file.
  
  Signed-off-by: Eric Blake <ebb9@byu.net>
  

Download

• doc/posix-functions/stdin.texi

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

Download