This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/12600] New: The "ERROR_NOT_AVAILABLE" error/exception isnot exposed to python
- From: "pedro at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 22 Mar 2011 15:43:47 +0000
- Subject: [Bug python/12600] New: The "ERROR_NOT_AVAILABLE" error/exception isnot exposed to python
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=12600
Summary: The "ERROR_NOT_AVAILABLE" error/exception is not
exposed to python
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: python
AssignedTo: unassigned@sourceware.org
ReportedBy: pedro@codesourcery.com
In <http://sourceware.org/ml/gdb-patches/2011-02/msg00163.html>:
> >>>>> "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.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.