diff options
| author | Simon Marchi <simon.marchi@ericsson.com> | 2015-10-21 15:57:22 -0400 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@ericsson.com> | 2015-10-21 15:57:22 -0400 |
| commit | bed91f4da252b5f30d3cb4fd9f9febd61ad9560d (patch) | |
| tree | 863ae6006d0e18b2f383713c3048d0e4287266ee /gdb/testsuite/ChangeLog | |
| parent | 3f2f83ddcba5b04389dd3c666ce7d4cace7e5b63 (diff) | |
| download | fsf-binutils-gdb-bed91f4da252b5f30d3cb4fd9f9febd61ad9560d.zip fsf-binutils-gdb-bed91f4da252b5f30d3cb4fd9f9febd61ad9560d.tar.gz fsf-binutils-gdb-bed91f4da252b5f30d3cb4fd9f9febd61ad9560d.tar.bz2 | |
Fix accessing a function's fields (parameters) from Python (PR 18073)
Since 7.4, gdb doesn't allow calling .fields() on a function type, even
though the documentation states it should return a list corresponding to
the function's parameters. This patch restores the intended behaviour
and adds a test for it.
Reg-tested on Arch Linux x86-64.
gdb/ChangeLog:
PR python/18073
* python/py-type.c (typy_get_composite): Allow returning a
function type.
gdb/testsuite/ChangeLog:
PR python/18073
* gdb.python/py-type.c (C::a_method): New.
(C::a_const_method): New.
(C::a_static_method): New.
(a_function): New.
* gdb.python/py-type.exp (test_fields): Test getting fields
from function and method.
Diffstat (limited to 'gdb/testsuite/ChangeLog')
| -rw-r--r-- | gdb/testsuite/ChangeLog | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 8f47cc1..1313aa2 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,13 @@ +2015-10-21 Simon Marchi <simon.marchi@polymtl.ca> + + PR python/18073 + * gdb.python/py-type.c (C::a_method): New. + (C::a_const_method): New. + (C::a_static_method): New. + (a_function): New. + * gdb.python/py-type.exp (test_fields): Test getting fields + from function and method. + 2015-10-21 Keven Boell <keven.boell@intel.com> * gdb.fortran/vla-alloc-assoc.exp: New file. |