public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zopolis0 <creatorsmithmdt@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Zopolis0 via Gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Segfault in libjava/prims.cc while compiling gcj
Date: Thu, 19 May 2022 22:22:25 +1000	[thread overview]
Message-ID: <CAEYL+X-id=5Spp+wU+9-eYwmZ-=7BsTvJ4+TL82m_=-7ZSZFdQ@mail.gmail.com> (raw)
In-Reply-To: <87r14pyf1x.fsf@oldenburg.str.redhat.com>

It's the same implementation from when it was removed, unless you mean code
outside of gcc/java and libjava, which in that case I could have made an
error copying it in or modernising it.

On Thu, May 19, 2022 at 8:47 PM Florian Weimer <fweimer@redhat.com> wrote:

> * Zopolis:
>
> > ../../../../gcj/libjava/prims.cc:182:23: internal compiler error:
> > Segmentation fault
> >   182 |     = new java::lang::NullPointerException;
> >       |                       ^~~~~~~~~~~~~~~~~~~~
>
> This is likely a bug in the CNI implementation, specific to your GCJ
> port.  Allocation of CNI classes is different from regular C++ classes.
>
> Thanks,
> Florian
>
>

  reply	other threads:[~2022-05-19 12:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18  9:23 Zopolis0
2022-05-18  9:59 ` Xi Ruoyao
2022-05-18 10:38   ` Zopolis0
2022-05-18 10:43     ` Jonathan Wakely
2022-05-18 10:45       ` Zopolis0
2022-05-18 10:57         ` Jonathan Wakely
2022-05-18 11:01           ` Xi Ruoyao
2022-05-18 23:20             ` Zopolis0
2022-05-19  4:32               ` Zopolis0
2022-05-19  8:06                 ` Xi Ruoyao
2022-05-20 10:50                   ` Zopolis0
2022-05-18 11:16           ` Zopolis0
2022-05-19 10:47 ` Florian Weimer
2022-05-19 12:22   ` Zopolis0 [this message]
2022-05-21  7:12     ` Zopolis0
2022-06-15  7:51       ` Zopolis0
2022-06-17  9:20         ` Zopolis0

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='CAEYL+X-id=5Spp+wU+9-eYwmZ-=7BsTvJ4+TL82m_=-7ZSZFdQ@mail.gmail.com' \
    --to=creatorsmithmdt@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=gcc-help@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).