This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
libgcj/9934: Bugs in natFileDescriptorPosix.cc:available()
- From: arenn at urbanophile dot com
- To: gcc-gnats at gcc dot gnu dot org
- Date: 4 Mar 2003 05:32:33 -0000
- Subject: libgcj/9934: Bugs in natFileDescriptorPosix.cc:available()
- Reply-to: arenn at urbanophile dot com
>Number: 9934
>Category: libgcj
>Synopsis: Bugs in natFileDescriptorPosix.cc:available()
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Mar 04 05:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Aaron M. Renn
>Release: CVS as of 2003-03-03
>Organization:
>Environment:
Linux Red Hat 8.0
>Description:
In java::io::FileDescriptor::available, call to lseek in HAVE_FSTAT block reverses parms. Should be lseek(fd, 0, SEEK_CUR) not lseek(fd, SEEK_CUR, 0)
Also, the last return value appears to be a fall through value that may or may not be what is intended. If fall through to zero is ok when various other methods fail, why not return zero when there is no implementation rather than throwing exception?
>How-To-Repeat:
N/A
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: