[Bug libfortran/35063] write statement leaks handles/memory on windows xp
jvdelisle at gcc dot gnu dot org
gcc-bugzilla@gcc.gnu.org
Mon Feb 4 04:36:00 GMT 2008
------- Comment #3 from jvdelisle at gcc dot gnu dot org 2008-02-04 04:35 -------
I did not see this on my first run because it scrolls by too fast on my
terminal.
==25454== Conditional jump or move depends on uninitialised value(s)
==25454== at 0x4333F1: strlen (in /home/jerry/prs/pr35063/a.out)
==25454== by 0x45DE74: fillin_rpath (in /home/jerry/prs/pr35063/a.out)
==25454== by 0x45FC35: _dl_init_paths (in /home/jerry/prs/pr35063/a.out)
==25454== by 0x439CDE: _dl_non_dynamic_init (in
/home/jerry/prs/pr35063/a.out)
==25454== by 0x43A3DA: __libc_init_first (in /home/jerry/prs/pr35063/a.out)
==25454== by 0x414CF5: (below main) (in /home/jerry/prs/pr35063/a.out)
==25454==
==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)
The end of the run shows:
==25454== Use of uninitialised value of size 8
==25454== at 0x41AB57: exit (in /home/jerry/prs/pr35063/a.out)
==25454==
==25454== ERROR SUMMARY: 12 errors from 3 contexts (suppressed: 0 from 0)
==25454== malloc/free: in use at exit: 0 bytes in 0 blocks.
==25454== malloc/free: 0 allocs, 0 frees, 0 bytes allocated.
==25454== For counts of detected errors, rerun with: -v
==25454== All heap blocks were freed -- no leaks are possible.
But no memory leaks reported. Still, its suspicious.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35063
More information about the Gcc-bugs
mailing list