This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Some Python ideas, looking for feedback
- From: Andrew Oakley <andrew at ado dot is-a-geek dot net>
- To: gdb-patches at sourceware dot org
- Cc: <gdb at sourceware dot org>
- Date: Wed, 17 Aug 2011 20:13:16 +0100
- Subject: Re: Some Python ideas, looking for feedback
- References: <09787EF419216C41A903FD14EE5506DD0151D583A2@AUSX7MCPC103.AMER.DELL.COM> <201108161345.33448.andre.poenitz@nokia.com> <09787EF419216C41A903FD14EE5506DD0151D585D2@AUSX7MCPC103.AMER.DELL.COM> <20110817193710.59945561@ado-gentoo>
On Wed, 17 Aug 2011 19:37:10 +0100
Andrew Oakley <andrew@ado.is-a-geek.net> wrote:
> What you are looking for is (for some reason) stored in bitpos. I
> can't actually find any documentation for this :(.
Perhaps we should fix that:
Document gdb.Value field attribute "bitpos" for enums.
---
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 6e7bf52..c82173b 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -21575,7 +21575,8 @@ Each field is an object, with some pre-defined
attributes: @item bitpos
This attribute is not available for @code{static} fields (as in
C@t{++} or Java). For non-@code{static} fields, the value is the bit
-position of the field.
+position of the field. For @code{enum} fields, the value is the
enumeration +member's integer representation.
@item name
The name of the field, or @code{None} for anonymous fields.
--
Andrew Oakley