public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: David Young <dvd@OCF.Berkeley.EDU>
To: tromey@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libgcj/8711: abnormal program termination during loop starts CPU overload
Date: Mon, 02 Dec 2002 18:26:00 -0000	[thread overview]
Message-ID: <20021203022602.29042.qmail@sources.redhat.com> (raw)

The following reply was made to PR libgcj/8711; it has been noted by GNATS.

From: David Young <dvd@OCF.Berkeley.EDU>
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
 >  
 >
 
 
 


             reply	other threads:[~2002-12-03  2:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-02 18:26 David Young [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-01 13:07 tromey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021203022602.29042.qmail@sources.redhat.com \
    --to=dvd@ocf.berkeley.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=tromey@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).