From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29057 invoked by alias); 3 Dec 2002 02:26:03 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 29043 invoked by uid 71); 3 Dec 2002 02:26:02 -0000 Date: Mon, 02 Dec 2002 18:26:00 -0000 Message-ID: <20021203022602.29042.qmail@sources.redhat.com> To: tromey@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: David Young Subject: Re: libgcj/8711: abnormal program termination during loop starts CPU overload Reply-To: David Young X-SW-Source: 2002-12/txt/msg00111.txt.bz2 List-Id: The following reply was made to PR libgcj/8711; it has been noted by GNATS. From: David Young To: tromey@gcc.gnu.org, davit@users.sourceforge.net, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, java-prs@gcc.gnu.org, nobody@gcc.gnu.org, tromey@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: libgcj/8711: abnormal program termination during loop starts CPU overload Date: Mon, 02 Dec 2002 18:16:36 -0800 tromey@gcc.gnu.org wrote: > I don't think this is a bug. > Ignoring the IOException allows this to happen. > After adding "System.exit(0)" within the catch clause, I still ran into the original behavior. Does the behavior result from the IOException? > I don't think there is any other behavior we could allow. > I believe the JDK does the same thing here. > I don't actually encounter the problem when I compile and run the test program with Sun's JDK 1.4.1 and close the console. If the behavior isn't a bug, might it be a useful feature enhancement? > Do you disagree? > >http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8711 > >