aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2025-03-27 14:20:04 +0100
committerTom de Vries <tdevries@suse.de>2025-03-27 14:20:04 +0100
commit9ab3eb8a513b5fa34477efa8bca27673a730740a (patch)
treed91db7c18c4802dba388e9262b63636fb6c77208
parentb5485cfa8dcef32a9e15e6e7835ab83abdc7502c (diff)
downloadbinutils-9ab3eb8a513b5fa34477efa8bca27673a730740a.zip
binutils-9ab3eb8a513b5fa34477efa8bca27673a730740a.tar.gz
binutils-9ab3eb8a513b5fa34477efa8bca27673a730740a.tar.bz2
[gdbserver] Fix typo in tracepoint.cc
Fix a typo: ... $ codespell --config gdbserver/setup.cfg gdbserver/tracepoint.cc gdbserver/tracepoint.cc:951: mistakingly ==> mistakenly ...
-rw-r--r--gdbserver/tracepoint.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdbserver/tracepoint.cc b/gdbserver/tracepoint.cc
index 5e3792e..97e41c0 100644
--- a/gdbserver/tracepoint.cc
+++ b/gdbserver/tracepoint.cc
@@ -948,7 +948,7 @@ struct ipa_trace_buffer_control
who wrote last to the buffer control structure. We need to freeze
any inferior writing to the buffer while GDBserver touches memory,
so that the inferior can correctly detect that GDBserver had been
- there, otherwise, it could mistakingly think its commit was
+ there, otherwise, it could mistakenly think its commit was
successful; that's implemented by simply having GDBserver set a
breakpoint the inferior hits if it is the critical region.