This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libgcj/8711: abnormal program termination during loop starts CPU overload
- From: tromey at gcc dot gnu dot org
- To: davit at users dot sf dot net, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, java-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, tromey at gcc dot gnu dot org
- Date: 1 Dec 2002 21:07:15 -0000
- Subject: Re: libgcj/8711: abnormal program termination during loop starts CPU overload
- Reply-to: tromey at gcc dot gnu dot org, davit at users dot sf dot net, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, java-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, tromey at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
Synopsis: abnormal program termination during loop starts CPU overload
Responsible-Changed-From-To: unassigned->tromey
Responsible-Changed-By: tromey
Responsible-Changed-When: Sun Dec 1 13:07:14 2002
Responsible-Changed-Why:
I'm handling this.
State-Changed-From-To: open->closed
State-Changed-By: tromey
State-Changed-When: Sun Dec 1 13:07:14 2002
State-Changed-Why:
I don't think this is a bug.
Ignoring the IOException allows this to happen.
I don't think there is any other behavior we could allow.
I believe the JDK does the same thing here.
Do you disagree?
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8711