From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19700 invoked by alias); 30 Apr 2002 19:36:22 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 19663 invoked by uid 61); 30 Apr 2002 19:36:21 -0000 Date: Tue, 30 Apr 2002 12:36:00 -0000 Message-ID: <20020430193620.19662.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, java-prs@gcc.gnu.org, nobody@gcc.gnu.org, pinskia@physics.uc.edu From: tromey@gcc.gnu.org Reply-To: tromey@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, java-prs@gcc.gnu.org, nobody@gcc.gnu.org, pinskia@physics.uc.edu, gcc-gnats@gcc.gnu.org Subject: Re: libgcj/6301: gij -jar does not work X-SW-Source: 2002-04/txt/msg01651.txt.bz2 List-Id: Synopsis: gij -jar does not work State-Changed-From-To: open->analyzed State-Changed-By: tromey State-Changed-When: Tue Apr 30 12:36:19 2002 State-Changed-Why: I looked at this a bit today. It is an obscure bug in BufferedReader. What happens is that we read a line that ends in \r\n. However our buffer ends just after the \r. (There is a lot of code in BufferedReader to handle this case.) However what follows is that Manifest calls mark(), read(), and finally reset() on the BufferedReader. This causes the BufferedReader to lose track of the fact that it was between \r and \n. Then our reading of the manifest gets off-kilter and from there things progressively get worse. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6301