From: Tom Tromey <tromey@redhat.com>
To: Christoph Mathys <eraserix@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: cast in gdb python results in virtual baseclass botch
Date: Thu, 14 Apr 2011 16:03:00 -0000 [thread overview]
Message-ID: <m3k4ewhlb5.fsf@fleche.redhat.com> (raw)
In-Reply-To: <BANLkTini00+LMH4JjDmNOWNe+2PMi+b3Lg@mail.gmail.com> (Christoph Mathys's message of "Wed, 13 Apr 2011 16:59:49 +0200")
>>>>> "Christoph" == Christoph Mathys <eraserix@gmail.com> writes:
Christoph> RuntimeError: virtual baseclass botch
Christoph> I use gdb 7.2, which apparently does not yet support dynamic_cast().
Christoph> Both variables are stored inside a boost::shared_ptr, and I try to
Christoph> cast to contained interface pointer to a specific implementation
Christoph> pointer.
Can you make a small, self-contained example program showing the bug?
That would be very helpful.
I am not sure under what circumstances "virtual baseclass botch" can
show up. The code is obscure.
Tom
prev parent reply other threads:[~2011-04-14 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 14:59 Christoph Mathys
2011-04-13 15:27 ` André Pönitz
2011-04-13 17:08 ` Christoph Mathys
2011-04-13 17:09 ` Christoph Mathys
2011-04-13 17:29 ` André Pönitz
2011-04-14 13:45 ` Christoph Mathys
2011-04-14 16:03 ` Tom Tromey [this message]
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=m3k4ewhlb5.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eraserix@gmail.com \
--cc=gdb@sourceware.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