gdb: Add a find method for RegisterDescriptorIterator
Adds a new method 'find' to the gdb.RegisterDescriptorIterator class, this allows gdb.RegisterDescriptor objects to be looked up directly by register name rather than having to iterate over all registers. This will be of use for a later commit. I've documented the new function in the manual, but I don't think a NEWS entry is required here, as, since the last release, the whole register descriptor mechanism is new, and is already mentioned in the NEWS file. gdb/ChangeLog: * python/py-registers.c: Add 'user-regs.h' include. (register_descriptor_iter_find): New function. (register_descriptor_iterator_object_methods): New static global methods array. (register_descriptor_iterator_object_type): Add pointer to methods array. gdb/testsuite/ChangeLog: * gdb.python/py-arch-reg-names.exp: Add additional tests. gdb/doc/ChangeLog: * python.texi (Registers In Python): Document new find function.
This commit is contained in:
parent
67411cbf63
commit
14fa8fb307
6 changed files with 84 additions and 1 deletions
|
@ -5755,6 +5755,15 @@ A @code{gdb.RegisterDescriptor} has the following read-only properties:
|
|||
The name of this register.
|
||||
@end defvar
|
||||
|
||||
It is also possible to lookup a register descriptor based on its name
|
||||
using the following @code{gdb.RegisterDescriptorIterator} function:
|
||||
|
||||
@defun RegisterDescriptorIterator.find (@var{name})
|
||||
Takes @var{name} as an argument, which must be a string, and returns a
|
||||
@code{gdb.RegisterDescriptor} for the register with that name, or
|
||||
@code{None} if there is no register with that name.
|
||||
@end defun
|
||||
|
||||
Python code can also request from a @code{gdb.Architecture}
|
||||
information about the set of register groups available on a given
|
||||
architecture
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue