public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tromey@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, java-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, pinskia@physics.uc.edu
Subject: Re: libgcj/6301: gij -jar does not work
Date: Tue, 30 Apr 2002 12:36:00 -0000	[thread overview]
Message-ID: <20020430193620.19662.qmail@sources.redhat.com> (raw)

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


             reply	other threads:[~2002-04-30 19:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-30 12:36 tromey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-30 16:56 Andrew Pinski
2002-04-30 16:54 tromey
2002-04-14  9:56 pinskia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020430193620.19662.qmail@sources.redhat.com \
    --to=tromey@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=pinskia@physics.uc.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).