public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	stefan@space.twc.de
Subject: Re: c++/9629: [3.2/3.3/3.4 regression] virtual inheritance segfault
Date: Fri, 14 Feb 2003 20:46:00 -0000	[thread overview]
Message-ID: <20030214204619.20336.qmail@sources.redhat.com> (raw)

Old Synopsis: virtual inheritance segfault
New Synopsis: [3.2/3.3/3.4 regression] virtual inheritance segfault

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Fri Feb 14 20:46:18 2003
State-Changed-Why:
    Confirmed. Here's a very slightly reduced testcase:
    --------------------------
    struct A { };
    
    struct B {
    	B(A *) {}
    };
    
    struct C : virtual public A, public B {
    	C() : B(this) {}
    };
    
    struct D : virtual public C {};
    
    main() {
      new D();
    }
    ------------------------
    Executing this program segfaults with 3.2.2, 3.3, and 3.4.
    So it is a regression, assuming the code is legal.
    
    The problem is in casting this to A* in the constructor
    C::C. It's trying to cast to a virtual base, and it seems
    to me that this information is not available at the time
    we get to C::C, which then causes the segfault. But that's
    just a wild guess.
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9629


             reply	other threads:[~2003-02-14 20:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-14 20:46 bangerth [this message]
2003-02-21 16:08 nathan
2003-03-17 11:52 nathan

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=20030214204619.20336.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=stefan@space.twc.de \
    /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).