public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "blitzmunter at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55453] New: Bug with virtual methods and objects with dtors.
Date: Fri, 23 Nov 2012 20:42:00 -0000	[thread overview]
Message-ID: <bug-55453-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 55453
           Summary: Bug with virtual methods and objects with dtors.
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: blitzmunter@gmail.com


Hi,

Mingw G++ appears to have a bug involving multiple inheritance and virtual
methods that return objects with dtors.

I have tried on 3 ditros - nuwen, tdm and the official mingw distro - and it
happens on all g++ versions >= 4.7.0.

It does not appear to occur on Linux, although I've only been able to test with
kubuntu12 and mint14, both of which have g++ 4.7.2 installed.

Even though this appears to be mingw specific, I've already posted this bug
report on the mingw bug reports system and they told me to post it here.

Anyway, see below code: The problem occurs when the 'interface method'
LinkResolver is called by the markdown object. The correct method is invoked,
but the 'this' pointer is messed up.

The trigger seems to be the String dtor. Remove this, or have the interface
method return a simple type, and it works as expected.

Bye!
Mark

//***** CODE ******

#include <stdio.h>

struct String {
    ~String() { }
};

struct Object {
    virtual ~Object() { }
};

struct LinkResolver {
    virtual String ResolveLink() = 0;
};

struct Docs : public Object, public virtual LinkResolver {
    Docs() {
        printf("       Docs::Docs() this: %p\n", this);
    }

    virtual String ResolveLink() {
        printf("Docs::ResolveLink() this: %p\n", this);
        return String();
    }
};

struct Markdown {
    LinkResolver * _resolver;

    Markdown(LinkResolver * resolver) : _resolver(resolver) { }

    void Go() {
        _resolver->ResolveLink();
    }
};

int main() {
    printf("GCC %d.%d.%d\n", __GNUC__, __GNUC_MINOR__, __GNUC_PATCHLEVEL__);

    Docs d;

    printf("             main()   &d: %p\n", &d);

    d.ResolveLink();

    Markdown m(&d);

    m.Go();
}


             reply	other threads:[~2012-11-23 20:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23 20:42 blitzmunter at gmail dot com [this message]
2012-11-23 21:45 ` [Bug c++/55453] " paolo.carlini at oracle dot com
2012-11-23 21:51 ` paolo.carlini at oracle dot com

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-55453-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).