--- Comment #6 from fxcoudert at gcc dot gnu dot org 2008-02-04 23:40
---
(In reply to comment #2)
> I have confirmed this under cygwin. Taking the READ statement out so the
> program can run unabated, leads to a system failure trying to allocate
> memory.
> This is platform specific,
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2008-02-04 21:05
---
Sorry for the confusion. I used:
print *,'Check memory and handles and press ENTER...', m
so I could track the progress. Without the m, I see no errors. Also notice
that he two upfront errors are in calls to
--- 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.
--- 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/
