libgcj/6293: PipedInputStream.close() does not notify writer (Mauve test)

mark@klomp.org mark@klomp.org
Sun Apr 14 06:46:00 GMT 2002


>Number:         6293
>Category:       libgcj
>Synopsis:       PipedInputStream.close() does not notify writer (Mauve test)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Apr 14 06:16:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     mark@klomp.org
>Release:        gcj 3.1
>Organization:
>Environment:

>Description:
According to the Mauve testlet gnu.testlet.java.io.PipedStream.close the PipedInputStream.close() method should notify the associated PipedOutputStream of the close.

We currently faily this test. But the testlet looks like it is actually testing wether a PipedInputStream.read() will return -1 when PipedInputStream.close() is called in another Thread. Anyway we fail this test.
>How-To-Repeat:
echo gnu.testlet.java.io.PipedStream.close | ./SimpleTestHarness
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the Gcc-bugs mailing list