public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/49314] md5test, shatest output FAILs on Tru64 UNIX
Date: Thu, 16 Jun 2011 20:52:00 -0000	[thread overview]
Message-ID: <bug-49314-8172-YrK8ukGYEL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49314-8172@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-06-16 20:51:00 UTC ---
> It has been a while, but I think either _Jv_NewStringUTF
> or _Jv_NewStringUtf8Const.  IIRC one of these is run
> during class initialization to turn string constants into
> String objects.

Thanks.  It turned out those were ok.

When I logged calls to JvNewByteArray, I found two:

JvNewByteArray: length = 1
JvNewByteArray: length = 0

The first one is as expected for "a", the second seems fishy: at the end
of java::lang::String::getBytes, bufpos was 0 and buflen 1, so a new
empty buffer was returned.

Looking further, this is a problem with iconv somehow: in
gnu::gcj::convert::Output_iconv::write, iconv_adapter returns -1 with
errno == EILSEQ.  Not understanding this iconv business at all, I have
no idea how this can happen.

    Rainer


  parent reply	other threads:[~2011-06-16 20:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07 17:28 [Bug libgcj/49314] New: " ro at gcc dot gnu.org
2011-06-16 17:01 ` [Bug libgcj/49314] " ro at gcc dot gnu.org
2011-06-16 17:45 ` tromey at gcc dot gnu.org
2011-06-16 18:20 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-06-16 18:58 ` tromey at gcc dot gnu.org
2011-06-16 20:52 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2011-06-17  9:58 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-06-17 13:04 ` dominiq at lps dot ens.fr
2011-06-17 13:09 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-06-17 14:04 ` howarth at nitro dot med.uc.edu
2011-06-17 14:08 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-06-17 16:17 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-06-18  5:56 ` howarth at nitro dot med.uc.edu
2011-06-20 14:31 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-06-21 12:11 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-06-21 13:59 ` ro at gcc dot gnu.org
2011-06-21 17:11 ` ro at gcc dot gnu.org
2011-06-21 17:13 ` ro at gcc dot gnu.org

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=bug-49314-8172-YrK8ukGYEL@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    /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).