diff options
| author | Tom de Vries <tdevries@suse.de> | 2024-10-08 08:24:13 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2024-10-08 08:24:13 +0200 |
| commit | 0576fe8146527d871558d82d3e4e99d85f2115a7 (patch) | |
| tree | 62f4cb2af514c69276e2da22ffb78ca34bade92a /gdb/testsuite/gdb.dwarf2 | |
| parent | 99fd53b19dddeb232e169cc5a3918a2adf7d3da2 (diff) | |
| download | binutils-0576fe8146527d871558d82d3e4e99d85f2115a7.zip binutils-0576fe8146527d871558d82d3e4e99d85f2115a7.tar.gz binutils-0576fe8146527d871558d82d3e4e99d85f2115a7.tar.bz2 | |
[gdb/contrib] Add more separators in spellcheck.sh
Add two more separators in spellcheck.sh: colon and comma.
Doing so triggers the "inbetween->between" rule, which gives an incorrect
result. Override this with "inbetween->between, in between, in-between" [1],
in a new file gdb/contrib/common-misspellings.txt.
Fix the following common misspellings:
...
everytime -> every time
sucess -> success
thru -> through
transfered -> transferred
inbetween -> between, in between, in-between
...
Verified with spellcheck.sh. Tested on x86_64-linux.
[1] https://www.grammarly.com/blog/commonly-confused-words/in-between-or-inbetween/
Diffstat (limited to 'gdb/testsuite/gdb.dwarf2')
| -rw-r--r-- | gdb/testsuite/gdb.dwarf2/dw2-step-out-of-function-no-stmt.exp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/testsuite/gdb.dwarf2/dw2-step-out-of-function-no-stmt.exp b/gdb/testsuite/gdb.dwarf2/dw2-step-out-of-function-no-stmt.exp index a59c637..55f4373 100644 --- a/gdb/testsuite/gdb.dwarf2/dw2-step-out-of-function-no-stmt.exp +++ b/gdb/testsuite/gdb.dwarf2/dw2-step-out-of-function-no-stmt.exp @@ -19,7 +19,7 @@ # # This sort of thing can occur in optimized code, f.i. here a slightly more # elaborate case with another is-stmt=no entry (the one with line number 12) -# inbetween: +# in between: # INDEX LINE ADDRESS IS-STMT # 12 13 0x00000000004003ed # 13 12 0x00000000004003f2 |