This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/35063] write statement leaks handles/memory on windows xp
- From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 4 Feb 2008 07:17:37 -0000
- Subject: [Bug libfortran/35063] write statement leaks handles/memory on windows xp
- References: <bug-35063-12481@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from tkoenig at gcc dot gnu dot org 2008-02-04 07:17 -------
(In reply to comment #3)
> ==25454== Conditional jump or move depends on uninitialised value(s)
> ==25454== at 0x4333BD: strlen (in /home/jerry/prs/pr35063/a.out)
> ==25454== by 0x408087: write_integer (write.c:612)
> ==25454== by 0x40AEDD: _gfortrani_list_formatted_write (write.c:785)
> ==25454== by 0x400330: MAIN__ (in /home/jerry/prs/pr35063/a.out)
> ==25454== by 0x40043B: main (fmain.c:21)
Strange. How did the code ever reach write_integer? There
is no integer I/O there. Could you maybe set a breakpoint and
check how it is reached?
Unfortunately, I can't reproduce a problem on i686-pc-linux-gnu.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063