aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.python
diff options
context:
space:
mode:
authorLancelot SIX <lancelot.six@amd.com>2023-03-10 15:34:26 +0000
committerLancelot SIX <lancelot.six@amd.com>2023-07-19 09:47:20 +0100
commit81dd93c85623960bf4b1f7c2e2d297a333e2ec52 (patch)
treed097fa8c045f614683a8a80d846a505c3dbe5465 /gdb/testsuite/gdb.python
parent0d332f11122473192a944230e1d925bac115ca0d (diff)
downloadbinutils-81dd93c85623960bf4b1f7c2e2d297a333e2ec52.zip
binutils-81dd93c85623960bf4b1f7c2e2d297a333e2ec52.tar.gz
binutils-81dd93c85623960bf4b1f7c2e2d297a333e2ec52.tar.bz2
gdb/amd-dbgapi-target: Use inf param in detach
Current implementation of amd_dbgapi_target::detach (inferior *, int) does the following: remove_breakpoints_inf (current_inferior ()); detach_amd_dbgapi (inf); beneath ()->detach (inf, from_tty); I find that using a mix of `current_inferior ()` and `inf` disturbing. At this point, we know that both are the same (target_detach does assert that `inf == current_inferior ()` before calling target_ops::detach). To improve consistency, this patch replaces `current_inferior ()` with `inf` in amd_dbgapi_target::detach. Change-Id: I01b7ba2e661c25839438354b509d7abbddb7c5ed Approved-By: Pedro Alves <pedro@palves.net>
Diffstat (limited to 'gdb/testsuite/gdb.python')
0 files changed, 0 insertions, 0 deletions