From: "André Pönitz" <andre.poenitz@nokia.com>
To: gdb@sourceware.org
Subject: Re: cast in gdb python results in virtual baseclass botch
Date: Wed, 13 Apr 2011 15:27:00 -0000 [thread overview]
Message-ID: <201104131726.55718.andre.poenitz@nokia.com> (raw)
In-Reply-To: <BANLkTini00+LMH4JjDmNOWNe+2PMi+b3Lg@mail.gmail.com>
On Wednesday 13 April 2011 16:59:49 ext Christoph Mathys wrote:
> I try to cast a gdb.Value to another type. There are cases where it
> works, and others where it doesn't, and I don't really know why. If it
> doesn't work, I get the following exception when I call cast():
> RuntimeError: virtual baseclass botch
>
> I use gdb 7.2, which apparently does not yet support dynamic_cast().
>
> Both variables are stored inside a boost::shared_ptr, and I try to
> cast to contained interface pointer to a specific implementation
> pointer.
I don't think you have to cast.
inner = item.value["px"].dereference() has already the correct type.
Andre'
next prev parent reply other threads:[~2011-04-13 15:27 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 [this message]
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
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=201104131726.55718.andre.poenitz@nokia.com \
--to=andre.poenitz@nokia.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