aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.arch
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2024-11-23 12:20:34 +0100
committerTom de Vries <tdevries@suse.de>2024-11-23 12:20:34 +0100
commitac51afb51c00693bb19c6a6110e9a45d2e4f79b7 (patch)
treeb2fcf9ded59d04633dbb406083e2814c34e4e468 /gdb/testsuite/gdb.arch
parent63eedf3b09f73077ecff2118f45d1adb1391eddd (diff)
downloadbinutils-ac51afb51c00693bb19c6a6110e9a45d2e4f79b7.zip
binutils-ac51afb51c00693bb19c6a6110e9a45d2e4f79b7.tar.gz
binutils-ac51afb51c00693bb19c6a6110e9a45d2e4f79b7.tar.bz2
[gdb/contrib] Add two rules in common-misspellings.txt
Eli mentioned [1] that given that we use US English spelling in our documentation, we should use "behavior" instead of "behaviour". In wikipedia-common-misspellings.txt there's a rule: ... behavour->behavior, behaviour ... which leaves this as a choice. Add an overriding rule to hardcode the choice to common-misspellings.txt: ... behavour->behavior ... and add a rule to rewrite behaviour into behavior: ... behaviour->behavior ... and re-run spellcheck.sh on gdb*. Tested on x86_64-linux. [1] https://sourceware.org/pipermail/gdb-patches/2024-November/213371.html
Diffstat (limited to 'gdb/testsuite/gdb.arch')
-rw-r--r--gdb/testsuite/gdb.arch/amd64-invalid-stack-middle.c2
-rw-r--r--gdb/testsuite/gdb.arch/amd64-invalid-stack-middle.exp2
-rw-r--r--gdb/testsuite/gdb.arch/amd64-invalid-stack-top.c2
-rw-r--r--gdb/testsuite/gdb.arch/amd64-invalid-stack-top.exp2
4 files changed, 4 insertions, 4 deletions
diff --git a/gdb/testsuite/gdb.arch/amd64-invalid-stack-middle.c b/gdb/testsuite/gdb.arch/amd64-invalid-stack-middle.c
index 7d8a667..1e0e957 100644
--- a/gdb/testsuite/gdb.arch/amd64-invalid-stack-middle.c
+++ b/gdb/testsuite/gdb.arch/amd64-invalid-stack-middle.c
@@ -58,7 +58,7 @@ func1 (void *ptr)
/* Finds and returns an invalid pointer, mmaps in a page, grabs a pointer
to it then unmaps the page again. This is almost certainly "undefined"
- behaviour, but should be good enough for this small test program. */
+ behavior, but should be good enough for this small test program. */
static void *
make_invalid_ptr (void)
diff --git a/gdb/testsuite/gdb.arch/amd64-invalid-stack-middle.exp b/gdb/testsuite/gdb.arch/amd64-invalid-stack-middle.exp
index 2423e76..d78c051 100644
--- a/gdb/testsuite/gdb.arch/amd64-invalid-stack-middle.exp
+++ b/gdb/testsuite/gdb.arch/amd64-invalid-stack-middle.exp
@@ -19,7 +19,7 @@
# frame where the stack in unreadable.
#
# One interesting bug that has been observed is that gdb will sometime
-# exhibit different behaviour the first time a stack command is run
+# exhibit different behavior the first time a stack command is run
# compared to the second (and later) times a command is run. This is
# because the first time a command is run gdb actually tries to figure out
# the answer, while the second (and later) times gdb relies on the answer
diff --git a/gdb/testsuite/gdb.arch/amd64-invalid-stack-top.c b/gdb/testsuite/gdb.arch/amd64-invalid-stack-top.c
index 8373693..445673c 100644
--- a/gdb/testsuite/gdb.arch/amd64-invalid-stack-top.c
+++ b/gdb/testsuite/gdb.arch/amd64-invalid-stack-top.c
@@ -42,7 +42,7 @@ func1 (void *ptr)
/* Finds and returns an invalid pointer, mmaps in a page, grabs a pointer
to it then unmaps the page again. This is almost certainly "undefined"
- behaviour, but should be good enough for this small test program. */
+ behavior, but should be good enough for this small test program. */
static void *
make_invalid_ptr (void)
diff --git a/gdb/testsuite/gdb.arch/amd64-invalid-stack-top.exp b/gdb/testsuite/gdb.arch/amd64-invalid-stack-top.exp
index 8571ca9..b58a75f 100644
--- a/gdb/testsuite/gdb.arch/amd64-invalid-stack-top.exp
+++ b/gdb/testsuite/gdb.arch/amd64-invalid-stack-top.exp
@@ -19,7 +19,7 @@
# frame where the stack in unreadable.
#
# One interesting bug that has been observed is that gdb will sometime
-# exhibit different behaviour the first time a stack command is run
+# exhibit different behavior the first time a stack command is run
# compared to the second (and later) times a command is run. This is
# because the first time a command is run gdb actually tries to figure out
# the answer, while the second (and later) times gdb relies on the answer