From ac51afb51c00693bb19c6a6110e9a45d2e4f79b7 Mon Sep 17 00:00:00 2001 From: Tom de Vries Date: Sat, 23 Nov 2024 12:20:34 +0100 Subject: [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 --- gdb/remote-fileio.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'gdb/remote-fileio.c') diff --git a/gdb/remote-fileio.c b/gdb/remote-fileio.c index 11cf2bb..fe6ac17 100644 --- a/gdb/remote-fileio.c +++ b/gdb/remote-fileio.c @@ -555,7 +555,7 @@ remote_fileio_func_read (remote_target *remote, char *buf) break; default: buffer = (gdb_byte *) xmalloc (length); - /* POSIX defines EINTR behaviour of read in a weird way. It's allowed + /* POSIX defines EINTR behavior of read in a weird way. It's allowed for read() to return -1 even if "some" bytes have been read. It has been corrected in SUSv2 but that doesn't help us much... Therefore a complete solution must check how many bytes have been -- cgit v1.1