This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [unavailable values part 1, 17/17] unavailable vptr / virtual base offset
- From: Tom Tromey <tromey at redhat dot com>
- To: Pedro Alves <pedro at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 07 Feb 2011 09:20:37 -0700
- Subject: Re: [unavailable values part 1, 17/17] unavailable vptr / virtual base offset
- References: <201102071435.55786.pedro@codesourcery.com>
>>>>> "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