aboutsummaryrefslogtreecommitdiff
path: root/gdb/break-catch-load.c
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@efficios.com>2023-05-08 15:45:52 -0400
committerSimon Marchi <simon.marchi@efficios.com>2023-05-25 08:46:23 -0400
commit26a69f095f1a2f534dcd347f28a9282dff0fde1f (patch)
tree311eac6a5c4d2af411813d4294aea5c282b6d987 /gdb/break-catch-load.c
parent7529ff1fcdbe260a0ac84ee8f33f4fa4ee1ac455 (diff)
downloadbinutils-26a69f095f1a2f534dcd347f28a9282dff0fde1f.zip
binutils-26a69f095f1a2f534dcd347f28a9282dff0fde1f.tar.gz
binutils-26a69f095f1a2f534dcd347f28a9282dff0fde1f.tar.bz2
gdb: get gdbarch from syscall_catchpoint instead of location
I noticed some methods of syscall_catchpoint doing this: struct gdbarch *gdbarch = loc->owner->gdbarch; `loc` is the list of locations of this catchpoint. Logically, the owner the locations are this catchpoint. So this just ends up getting this->gdbarch. Remove the unnecessary indirection through the loc. syscall_catchpoint::print_recreate does something slightly different, getting its arch from the loc: struct gdbarch *gdbarch = loc->gdbarch; I suppose it's always going to be the same arch, so get it from the catchpoint there too. Change-Id: I6f6a6f8e0cd7cfb754cecfb6249e71ec12ba4855 Reviewed-By: Alexandra Petlanova Hajkova <ahajkova@redhat.com> Reviewed-By: Andrew Burgess <aburgess@redhat.com>
Diffstat (limited to 'gdb/break-catch-load.c')
0 files changed, 0 insertions, 0 deletions