diff options
author | Joel Brobecker <brobecker@adacore.com> | 2013-12-23 11:15:42 +0400 |
---|---|---|
committer | Joel Brobecker <brobecker@adacore.com> | 2013-12-28 07:19:07 +0400 |
commit | 0809504b5eca5e73ad721919b6b13d941ffd0a30 (patch) | |
tree | c56723b5e2d0f31798f0bfb01c50679dfec89f9a /Makefile.def | |
parent | edef60002fc0c8d1bda6b5deb03c84d2733a32ba (diff) | |
download | gdb-0809504b5eca5e73ad721919b6b13d941ffd0a30.zip gdb-0809504b5eca5e73ad721919b6b13d941ffd0a30.tar.gz gdb-0809504b5eca5e73ad721919b6b13d941ffd0a30.tar.bz2 |
Fix gdb.Field attributes documentation for enum types.
The following patch ...
| commit 14e75d8ea4fe9ed4dbf292ae4a9745e33e2ff353
| Date: Wed Apr 18 06:46:47 2012 +0000
|
| gdb/
| PR symtab/7259:
| [...]
... discussed under ...
[PATCH] Allow 64-bit enum values
http://www.sourceware.org/ml/gdb-patches/2012-03/msg00772.html
... introduced a change in the gdb.Fields API without documenting it:
| I took a separate approach from the one I took in:
|
| http://sourceware.org/ml/gdb-patches/2012-02/msg00403.html
|
| and removed the overloaded meaning of the bitpos location variable to
| fix PR symtab/7259. In the following patch, I introduce a separate
| field_location union member 'enumval' which can accept LONGEST and
| hence expand enum values to 64-bit signed values. With this change,
| bitpos now only is used for (non-negative) offsets into structures,
| since the other overload of bitpos (range bounds) were already
| separated into struct range_bound.
This patch updates the documentation to reflect that change.
gdb/doc/ChangeLog:
* gdb.texinfo (Types In Python): Fix the documentation of
attribute "bitpos" in class gdb.Field for enum types. Add
documentation for attribute "enumval" in that same class.
Diffstat (limited to 'Makefile.def')
0 files changed, 0 insertions, 0 deletions