This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
libgcj/6183: BufferedByteOutputStream doesn't handle InterruptedIOException correctly
- From: mark at klomp dot org
- To: gcc-gnats at gcc dot gnu dot org
- Date: 5 Apr 2002 00:09:16 -0000
- Subject: libgcj/6183: BufferedByteOutputStream doesn't handle InterruptedIOException correctly
- Reply-to: mark at klomp dot org
>Number: 6183
>Category: libgcj
>Synopsis: BufferedByteOutputStream doesn't handle InterruptedIOException correctly
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Apr 04 16:16:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: mark@klomp.org
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
The mauve test for BufferedByteOutputStream.interrupt fails since the BufferedByteOutputStream does not handle a InterruptedIOException in the underlying stream correctly.
Tom Tromey writes:
I think I wrote this test. It is pretty optimistic. I seem to recall
general agreement that InterruptedIOException couldn't really be
relied on, since even Sun didn't fully implement it on all platforms.
The test has been added to the xfails list of the libjava.mauve testsuite.
>How-To-Repeat:
In your configured and compiled mauve obj dir do:
echo gnu.testlet.java.io.BufferedByteOutputStream.interrupt | ./SimpleTestHarness
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: