aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.threads/slow-waitpid.c
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.threads/slow-waitpid.c
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.threads/slow-waitpid.c')
-rw-r--r--gdb/testsuite/gdb.threads/slow-waitpid.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/gdb/testsuite/gdb.threads/slow-waitpid.c b/gdb/testsuite/gdb.threads/slow-waitpid.c
index 25052c3..280b109 100644
--- a/gdb/testsuite/gdb.threads/slow-waitpid.c
+++ b/gdb/testsuite/gdb.threads/slow-waitpid.c
@@ -19,7 +19,7 @@
using the LD_PRELOAD technique.
The library intercepts calls to WAITPID and SIGSUSPEND in order to
- simulate the behaviour of a heavily loaded kernel.
+ simulate the behavior of a heavily loaded kernel.
When GDB wants to stop all threads in an inferior each thread is sent a
SIGSTOP, GDB will then wait for the signal to be received by the thread
@@ -39,7 +39,7 @@
The idea in this library is to rate limit calls to waitpid (where pid is
-1 and the WNOHANG option is set) so that only 1 per second can return
an answer. Any additional calls will report that no threads are
- currently ready. This should match the behaviour we see on a slow
+ currently ready. This should match the behavior we see on a slow
kernel.
However, given that usually when using this library, the kernel does