From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [unavailable values part 1, 17/17] unavailable vptr / virtual base offset
Date: Mon, 07 Feb 2011 16:20:00 -0000 [thread overview]
Message-ID: <m3tygfzui2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201102071435.55786.pedro@codesourcery.com> (Pedro Alves's message of "Mon, 7 Feb 2011 14:35:55 +0000")
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
Pedro> The patch adds a new ERROR_NOT_AVAILABLE error, thrown whenever
Pedro> something wants to get at a value's contents with value_contents()
Pedro> and makes baseclass_offset callers that care to handle errors
Pedro> getting at the base class offset gracefully catch the error.
This seems like something we could meaningfully expose to Python.
That is, we could expose this as a separate exception class, and update
gdb.Value to throw it and to expose the needed availability API.
Could you file a bug report about this?
Unless you are adding this later, that is.
Tom
next prev parent reply other threads:[~2011-02-07 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 14:36 Pedro Alves
2011-02-07 16:20 ` Tom Tromey [this message]
2011-02-10 18:48 ` Pedro Alves
2011-03-22 16:29 ` Pedro Alves
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=m3tygfzui2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
/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