[gdb/contrib] Handle dot in spellcheck.sh

Add handling of '.' in gdb/contrib/spellcheck.sh.

While we're at, simplify the sed invocation by using a single s command
instead of 3 s commands.

Also introduce sed_join and grep_join.

Fix the following common misspellings:
...
bandwith -> bandwidth
emmitted -> emitted
immediatly -> immediately
suprize -> surprise
thru -> through
transfered -> transferred
...

Verified with shellcheck.

5 files changed, 6 insertions, 6 deletions

diff --git a/gdb/testsuite/gdb.base/bigcore.exp b/gdb/testsuite/gdb.base/bigcore.exp
index 6c64d40..5e09d2f 100644
--- a/gdb/testsuite/gdb.base/bigcore.exp
+++ b/gdb/testsuite/gdb.base/bigcore.exp
@@ -25,7 +25,7 @@ require isnative
 # Can the system run this test (in particular support sparse
 # corefiles)?  On systems that lack sparse corefile support this test
 # consumes too many resources - gigabytes worth of disk space and
-# I/O bandwith.
+# I/O bandwidth.
 
 if { [istarget "*-*-*bsd*"]
      || [istarget "*-*-solaris*"] 
diff --git a/gdb/testsuite/gdb.base/call-sc.exp b/gdb/testsuite/gdb.base/call-sc.exp
index 91a4e5b..3a83d96 100644
--- a/gdb/testsuite/gdb.base/call-sc.exp
+++ b/gdb/testsuite/gdb.base/call-sc.exp
@@ -286,7 +286,7 @@ proc test_scalar_returns { } {
 	}
 	-re ".*${gdb_prompt} $" {
 	    if $return_value_unimplemented {
-		# What a suprize.  The architecture hasn't implemented
+		# What a surprise.  The architecture hasn't implemented
 		# return_value, and hence has to fail.
 		kfail "$test" gdb/1444
 	    } else {
diff --git a/gdb/testsuite/gdb.base/structs.exp b/gdb/testsuite/gdb.base/structs.exp
index 7f1192d..ab68da2 100644
--- a/gdb/testsuite/gdb.base/structs.exp
+++ b/gdb/testsuite/gdb.base/structs.exp
@@ -376,7 +376,7 @@ proc test_struct_returns { n } {
 	}
 	-re ".*${gdb_prompt} $" {
 	    if $return_value_unimplemented {
-		# What a suprize.  The architecture hasn't implemented
+		# What a surprise.  The architecture hasn't implemented
 		# return_value, and hence has to fail.
 		kfail "$test" gdb/1444
 	    } else {
diff --git a/gdb/testsuite/gdb.debuginfod/build-id-no-debug-warning.exp b/gdb/testsuite/gdb.debuginfod/build-id-no-debug-warning.exp
index aa1c263..0819aae 100644
--- a/gdb/testsuite/gdb.debuginfod/build-id-no-debug-warning.exp
+++ b/gdb/testsuite/gdb.debuginfod/build-id-no-debug-warning.exp
@@ -16,7 +16,7 @@
 # This test triggers the "separate debug info file has no debug info" warning by replacing
 # the build-id based .debug file with the stripped binary and then loading it to gdb.
 # It then also sets up local debuginfod server with the correct debug file to download
-# to make sure no warnings are emmitted.
+# to make sure no warnings are emitted.
 
 
 standard_testfile
diff --git a/gdb/testsuite/gdb.mi/mi-memory-changed.exp b/gdb/testsuite/gdb.mi/mi-memory-changed.exp
index 486c4d7..6d9e504 100644
--- a/gdb/testsuite/gdb.mi/mi-memory-changed.exp
+++ b/gdb/testsuite/gdb.mi/mi-memory-changed.exp
@@ -44,11 +44,11 @@ mi_gdb_test "-var-create var_c * C" \
 
 mi_gdb_test "-var-assign var_c 5" \
     "-var-assign var_c 5\r\n\\^done,value=\"5\"" \
-    "change C thru. varobj"
+    "change C through. varobj"
 
 mi_gdb_test  "-data-write-memory-bytes &C \"00\"" \
     {\^done} \
-    "change C thru. -data-write-memory-bytes"
+    "change C through. -data-write-memory-bytes"
 
 # Modify code section also triggers MI notification.