aboutsummaryrefslogtreecommitdiff
path: root/gas/frags.c
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2022-09-01 14:01:11 +0100
committerAndrew Burgess <aburgess@redhat.com>2022-10-02 14:21:24 +0100
commit7df4240040277fb752fd010f5a947cf2d32bc3a5 (patch)
treea32440970f906c64b01f1d547a583250b0dcb76c /gas/frags.c
parent9a103324fee16bf4d0bc4fa7b19f5d937d47b881 (diff)
downloadgdb-7df4240040277fb752fd010f5a947cf2d32bc3a5.zip
gdb-7df4240040277fb752fd010f5a947cf2d32bc3a5.tar.gz
gdb-7df4240040277fb752fd010f5a947cf2d32bc3a5.tar.bz2
gdb: add asserts to gdbarch_register_name
This commit adds asserts to gdbarch_register_name that validate the parameters, and the return value. The interesting thing here is that gdbarch_register_name is generated by gdbarch.py, and so, to add these asserts, I need to update the generation script. I've added two new arguments for Functions and Methods (as declared in gdbarch-components.py), these arguments are 'param_checks' and 'result_checks'. Each of these new arguments can be used to list some expressions that are then used within gdb_assert calls in the generated code. The asserts that validate the API as described in the comment I added to gdbarch_register_name a few commits back; the register number passed in needs to be a valid cooked register number, and the result being returned should not be nullptr.
Diffstat (limited to 'gas/frags.c')
0 files changed, 0 insertions, 0 deletions