[binutils-gdb] [gdb/testsuite] Make gdb.mi codespell-clean

Tom de Vries vries@sourceware.org
Tue May 20 09:06:55 GMT 2025


https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=1226dde9ef7555a5d28228c60eb4e3c5bcfa71b0

commit 1226dde9ef7555a5d28228c60eb4e3c5bcfa71b0
Author: Tom de Vries <tdevries@suse.de>
Date:   Tue May 20 11:05:55 2025 +0200

    [gdb/testsuite] Make gdb.mi codespell-clean
    
    Make gdb.mi codespell-clean and add the dir to the pre-commit
    configuration.
    
    Approved-By: Tom Tromey <tom@tromey.com>

Diff:
---
 .pre-commit-config.yaml                             | 2 +-
 gdb/testsuite/gdb.mi/mi-condbreak-throw.exp         | 2 +-
 gdb/testsuite/gdb.mi/mi-multi-commands.exp          | 2 +-
 gdb/testsuite/gdb.mi/mi-var-display.exp             | 4 ++--
 gdb/testsuite/gdb.mi/user-selected-context-sync.exp | 2 +-
 5 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index 116502a47fc..0eb727eeb6b 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -70,7 +70,7 @@ repos:
     rev: v2.4.1
     hooks:
     - id: codespell
-      files: '^(gdbsupport|gdbserver|gdb/(tui|target|data-directory|po|system-gdbinit|mi|syscalls|arch|regformats|compile|python|guile|config|unittests|cli|testsuite/gdb.(ctf|dap|gdb|go|modula2|objc|opencl|opt|pascal|perf|replay|reverse|rocm|server|stabs|testsuite|tui|xml)))/'
+      files: '^(gdbsupport|gdbserver|gdb/(tui|target|data-directory|po|system-gdbinit|mi|syscalls|arch|regformats|compile|python|guile|config|unittests|cli|testsuite/gdb.(ctf|dap|gdb|go|mi|modula2|objc|opencl|opt|pascal|perf|replay|reverse|rocm|server|stabs|testsuite|tui|xml)))/'
       args: [--config, gdb/contrib/setup.cfg]
   - repo: local
     hooks:
diff --git a/gdb/testsuite/gdb.mi/mi-condbreak-throw.exp b/gdb/testsuite/gdb.mi/mi-condbreak-throw.exp
index 9897b2bb31d..0a89a8a99bc 100644
--- a/gdb/testsuite/gdb.mi/mi-condbreak-throw.exp
+++ b/gdb/testsuite/gdb.mi/mi-condbreak-throw.exp
@@ -16,7 +16,7 @@
 # Check that when GDB fails to evaluate the condition of a conditional
 # breakpoint we only get one *stopped notification.  In this test case
 # the breakpoint condition fails due to throwing an uncaught C++
-# excpetion.
+# exception.
 
 require allow_cplus_tests
 
diff --git a/gdb/testsuite/gdb.mi/mi-multi-commands.exp b/gdb/testsuite/gdb.mi/mi-multi-commands.exp
index 20b8d46a934..3bc63eb2747 100644
--- a/gdb/testsuite/gdb.mi/mi-multi-commands.exp
+++ b/gdb/testsuite/gdb.mi/mi-multi-commands.exp
@@ -90,7 +90,7 @@ proc run_test { args } {
 	# looking for.  However, due to the unpredictable
 	# intermingling, it's much easier if we drop the ^ anchor.
 	# However, with this gone dejagnu would sometimes match the
-	# second comand output before the first commands output.
+	# second command output before the first commands output.
 	#
 	# This approach just looks for the first command output, then,
 	# once that has been found, we start looking for the second
diff --git a/gdb/testsuite/gdb.mi/mi-var-display.exp b/gdb/testsuite/gdb.mi/mi-var-display.exp
index 61b3894ce92..553536852f6 100644
--- a/gdb/testsuite/gdb.mi/mi-var-display.exp
+++ b/gdb/testsuite/gdb.mi/mi-var-display.exp
@@ -96,7 +96,7 @@ mi_gdb_test "-var-evaluate-expression bar" \
 # Desc: change value of bar
 mi_gdb_test "-var-assign bar 3" \
 	"\\^done,value=\"0x3\"" \
-	"assing to variable bar"
+	"assign to variable bar"
 
 mi_gdb_test "-var-set-format bar decimal" \
 	"\\^done,format=\"decimal\",value=\"3\"" \
@@ -152,7 +152,7 @@ mi_gdb_test "-var-evaluate-expression foo" \
 # Desc: change value of foo
 mi_gdb_test "-var-assign foo 3" \
 	"\\^done,value=\"03\"" \
-	"assing to variable foo"
+	"assign to variable foo"
 
 mi_gdb_test "-var-set-format foo decimal" \
 	"\\^done,format=\"decimal\",value=\"3\"" \
diff --git a/gdb/testsuite/gdb.mi/user-selected-context-sync.exp b/gdb/testsuite/gdb.mi/user-selected-context-sync.exp
index 9198cfbb727..ec22538d30b 100644
--- a/gdb/testsuite/gdb.mi/user-selected-context-sync.exp
+++ b/gdb/testsuite/gdb.mi/user-selected-context-sync.exp
@@ -985,7 +985,7 @@ proc_with_prefix test_mi_stack_select_frame { mode } {
 
 	# Now use the '-stack-select-frame' command with the --frame
 	# option, this verifies that even when the frame GDB would
-	# swith to is the same as the frame specified with --frame, an
+	# switch to is the same as the frame specified with --frame, an
 	# event is still sent to the CLI.
 
 	set cli_re [make_cli_re $mode -1 -1 0]


More information about the Binutils-cvs mailing list