public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "wmahan at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/23620] [4.0/4.1 Regression] Segfault compiling inner interfaces
Date: Wed, 31 Aug 2005 16:24:00 -0000 [thread overview]
Message-ID: <20050831162357.14358.qmail@sourceware.org> (raw)
In-Reply-To: <20050829094413.23620.wmahan@gmail.com>
------- Additional Comments From wmahan at gmail dot com 2005-08-31 16:23 -------
I guess that is a bug in my test case. I didn't notice because it compiles fine
with gcc 4.0.1 when A.class and A$AInt.class are not present.
The problem seems to be that when check_inner_circular_reference() is looking
for circular references, it segfaults when it gets to the tree for A, which has
->type.binfo == NULL. I'm not sure if that's supposed to happen.
Here's a patch that fixes the bug for me, but it may just fix the symptom rather
than the real problem.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23620
next prev parent reply other threads:[~2005-08-31 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 9:44 [Bug java/23620] New: " wmahan at gmail dot com
2005-08-30 10:56 ` [Bug java/23620] " pinskia at gcc dot gnu dot org
2005-08-31 15:26 ` [Bug java/23620] [4.0/4.1 Regression] " pinskia at gcc dot gnu dot org
2005-08-31 16:24 ` wmahan at gmail dot com [this message]
2005-09-01 19:18 ` wmahan at gmail dot com
2005-09-01 21:37 ` pinskia at gcc dot gnu dot org
2005-09-02 7:13 ` nathan at gcc dot gnu dot org
2005-09-21 14:29 ` tromey at gcc dot gnu dot org
[not found] <bug-23620-11253@http.gcc.gnu.org/bugzilla/>
2005-10-14 8:47 ` cvs-commit at gcc dot gnu dot org
2005-10-14 8:48 ` nathan at gcc dot gnu dot org
2005-10-14 8:48 ` cvs-commit at gcc dot gnu dot org
2005-10-14 12:09 ` pinskia at gcc dot gnu dot org
2005-10-14 12:09 ` pinskia at gcc dot gnu dot 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=20050831162357.14358.qmail@sourceware.org \
--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).