[Bug libfortran/31297] New: Use of uninitialized variables in libgfortran's I/O

[burnus at gcc dot gnu dot org]

Found using valgrind:

gfortran gfortran.dg/backspace_5.f
valgrind ./a.out

==15340== Syscall param write(buf) points to uninitialised byte(s)
==15340==    at 0x56000C0: __write_nocancel (in /lib64/libc-2.5.so)
==15340==    by 0x4EBEE90: do_write (unix.c:336)
==15340==    by 0x4EBEF31: fd_flush (unix.c:386)
==15340==    by 0x4EBCBF6: _gfortran_st_write_done (transfer.c:2762)
==15340==    by 0x400BAB: MAIN__ (in
/projects/tob/gcc/gcc/testsuite/gfortran.dg/a.out)
==15340==    by 0x40104B: main (fmain.c:22)

Similarly for:
- backspace_6.f
- write_back.f
- write_rewind_1.f
- write_rewind_2.f
- char_bounds_check_fail_1.f90
- direct_io_2.f90
- unf_io_convert_3.f90


-- 
           Summary: Use of uninitialized variables in libgfortran's I/O
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Keywords: wrong-code
          Severity: normal
          Priority: P3
         Component: libfortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: burnus at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31297