[Bug classpath/49814] New: Reading (resp. writing) from Pipe.SourceChannel (resp. to Pipe.SinkChannel) fails

[quentin.sabah at gmail dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49814

           Summary: Reading (resp. writing) from Pipe.SourceChannel (resp.
                    to Pipe.SinkChannel) fails
           Product: classpath
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: classpath
        AssignedTo: address@hidden
        ReportedBy: address@hidden


Reading (resp. writing) from Pipe.SourceChannel (resp. Pipe.SinkChannel) fails.
At the lowest level, reading and writing ends of the pipe are mixed up. In the
current implementation, read operations are carried against the write-only
file-descriptor of the (unix) pipe and write operations are carried against the
read-only file-descriptor.

The solution consists in reversing the affectation of the pipe's file
descriptors to their respective (Sink/Source)Channel. This modification is
possible at two locations:
 - in the gnu.java.nio.PipeImpl constructor
 - or in the JNI implementation of VMPipe.pipe()
 Depending on the semantic given to the return value of VMPipe.pipe().