public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/43086]  New: PR16923 fails with Assertion failed: (class_id)
Date: Mon, 15 Feb 2010 22:10:00 -0000	[thread overview]
Message-ID: <bug-43086-11113@http.gcc.gnu.org/bugzilla/> (raw)

On x86_64-apple-darwin9/10, the PR16923 libjava testcase, when linked to the
proper libiconv, fails with...

Assertion failed: (class_id), function main, file
/sw/src/fink.build/gcc44-4.4.2-1000/gcc-4.4.2/libjava/testsuite/libjava.jni/invocation/PR16923.c,
line 35.
Abort

A build of gcc-4.4.2 with the libgcc built with -O0 shows a backtrace of this
failure as...

#0  _Jv_AllocPtrFreeObj [inlined] () at java-gc.h:55
#1  _Jv_AllocString (len=Cannot access memory at address 0xf
) at ../../../gcc-4.4.2/libjava/prims.cc:627
Cannot access memory at address 0xf


-- 
           Summary: PR16923 fails with Assertion failed: (class_id)
           Product: gcc
           Version: 4.4.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: howarth at nitro dot med dot uc dot edu
 GCC build triplet: x86_64-apple-darwin*
  GCC host triplet: x86_64-apple-darwin*
GCC target triplet: x86_64-apple-darwin*


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


             reply	other threads:[~2010-02-15 22:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15 22:10 howarth at nitro dot med dot uc dot edu [this message]
2010-02-15 22:12 ` [Bug java/43086] " howarth at nitro dot med dot uc dot edu
2010-04-21 18:39 ` mrs at gcc dot gnu dot org
2010-04-21 19:02 ` mrs at gcc dot gnu dot org
2010-04-21 23:19 ` howarth at nitro dot med dot uc dot edu

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-43086-11113@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).