diff options
Diffstat (limited to 'gdb/testsuite')
32 files changed, 42 insertions, 42 deletions
diff --git a/gdb/testsuite/Makefile.in b/gdb/testsuite/Makefile.in index f799f16..3235c70 100644 --- a/gdb/testsuite/Makefile.in +++ b/gdb/testsuite/Makefile.in @@ -209,7 +209,7 @@ endif # in the same situation, we avoid invoking DejaGnu, and instead just call # the check/no-matching-tests-found rule (which prints a helpful message). # -# To get the same behaviour for check-single we decide here, based on how +# To get the same behavior for check-single we decide here, based on how # TESTS expanded, whether check-single should redirect to do-check-single or # to check/no-matching-tests-found. ifeq ($(expanded_tests_or_none),no-matching-tests-found) 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 diff --git a/gdb/testsuite/gdb.base/bt-on-fatal-signal.exp b/gdb/testsuite/gdb.base/bt-on-fatal-signal.exp index 9bed64a..81a634d 100644 --- a/gdb/testsuite/gdb.base/bt-on-fatal-signal.exp +++ b/gdb/testsuite/gdb.base/bt-on-fatal-signal.exp @@ -13,7 +13,7 @@ # You should have received a copy of the GNU General Public License # along with this program. If not, see <http://www.gnu.org/licenses/>. -# Test the 'maint set backtrace-on-fatal-signal' behaviour. Start up +# Test the 'maint set backtrace-on-fatal-signal' behavior. Start up # GDB, turn on backtrace-on-fatal-signal, then send fatal signals to # GDB and ensure we see the backtrace. diff --git a/gdb/testsuite/gdb.base/cached-source-file.exp b/gdb/testsuite/gdb.base/cached-source-file.exp index a2df5dc..b063362 100644 --- a/gdb/testsuite/gdb.base/cached-source-file.exp +++ b/gdb/testsuite/gdb.base/cached-source-file.exp @@ -124,7 +124,7 @@ file rename -force -- $bkpsrc $srcfile # As before, delay so that at least one second has passed. GDB still # will not spot that the source file has changed, as GDB doesn't do a # time check unless the binary has also changed, this delay just -# allows us to confirm this behaviour. +# allows us to confirm this behavior. sleep 1 # List the printf line again, we should not see the file changes yet diff --git a/gdb/testsuite/gdb.base/callexit.exp b/gdb/testsuite/gdb.base/callexit.exp index 692d9d0..f2b0838 100644 --- a/gdb/testsuite/gdb.base/callexit.exp +++ b/gdb/testsuite/gdb.base/callexit.exp @@ -33,7 +33,7 @@ if { ![runto_main] } { return 0 } -# Verify set may-call-functions behaviour. +# Verify set may-call-functions behavior. gdb_test_no_output "set may-call-functions off" gdb_test "call callexit()" \ "Cannot call functions in the program: may-call-functions is off." \ diff --git a/gdb/testsuite/gdb.base/condbreak.exp b/gdb/testsuite/gdb.base/condbreak.exp index 3b619e4..1f07bb5 100644 --- a/gdb/testsuite/gdb.base/condbreak.exp +++ b/gdb/testsuite/gdb.base/condbreak.exp @@ -252,7 +252,7 @@ gdb_test "with breakpoint pending off -- break main ta 999 if (1==1)" \ # as " - force - condition", that is, subtraction of the symbol # "force" followed by subtraction of symbol "context". This is really # just a quirk of how this used to be implemented, and should maybe be -# changed in the future. However, for now GDB retains this behaviour. +# changed in the future. However, for now GDB retains this behavior. gdb_test "break *main if (1==1) -force-condition" \ "No symbol \"force\" in current context\\." diff --git a/gdb/testsuite/gdb.base/define-prefix.exp b/gdb/testsuite/gdb.base/define-prefix.exp index 5695c1a..81d3a56 100644 --- a/gdb/testsuite/gdb.base/define-prefix.exp +++ b/gdb/testsuite/gdb.base/define-prefix.exp @@ -152,7 +152,7 @@ gdb_test "abc-prefix def-prefix ghi-prefix-cmd alternate-jkl-cmd" \ "use user command after redefining ghi-prefix-cmd: alternate-jkl-cmd" #################### -# Check error behaviour. +# Check error behavior. gdb_test "define-prefix print" ".* is built-in.*" diff --git a/gdb/testsuite/gdb.base/exitsignal.exp b/gdb/testsuite/gdb.base/exitsignal.exp index 85fd956..2d6fc03 100644 --- a/gdb/testsuite/gdb.base/exitsignal.exp +++ b/gdb/testsuite/gdb.base/exitsignal.exp @@ -80,7 +80,7 @@ gdb_test "print \$_exitsignal" " = 11" \ gdb_test "print \$_exitcode" " = void" \ "\$_exitcode is still void after restarting the inferior" -# Now we test the behaviour of $_exit{code,signal} during a normal +# Now we test the behavior of $_exit{code,signal} during a normal # inferior execution. standard_testfile normal.c diff --git a/gdb/testsuite/gdb.base/until-trailing-insns.exp b/gdb/testsuite/gdb.base/until-trailing-insns.exp index baa5f1f..ffd5df8 100644 --- a/gdb/testsuite/gdb.base/until-trailing-insns.exp +++ b/gdb/testsuite/gdb.base/until-trailing-insns.exp @@ -74,7 +74,7 @@ # range. It is only when GDB exits the loop that we leave the stepping # range, and the stepping finishes at address 0x114. # -# This test checks this behaviour using the DWARF assembler. +# This test checks this behavior using the DWARF assembler. load_lib dwarf.exp diff --git a/gdb/testsuite/gdb.base/wrap-line.exp b/gdb/testsuite/gdb.base/wrap-line.exp index 323cd6c..d5001bf 100644 --- a/gdb/testsuite/gdb.base/wrap-line.exp +++ b/gdb/testsuite/gdb.base/wrap-line.exp @@ -20,7 +20,7 @@ require {!is_remote host} # Test both ansi (no auto-wrap) and xterm (auto-wrap). Also test dumb, which -# shows the effective behaviour on stub-termcap systems, regardless of the +# shows the effective behavior on stub-termcap systems, regardless of the # TERM setting. set terms {ansi xterm dumb} diff --git a/gdb/testsuite/gdb.btrace/ptwrite.exp b/gdb/testsuite/gdb.btrace/ptwrite.exp index 0970d31..7f1adad 100644 --- a/gdb/testsuite/gdb.btrace/ptwrite.exp +++ b/gdb/testsuite/gdb.btrace/ptwrite.exp @@ -145,7 +145,7 @@ with_test_prefix "Custom" { ] } -### 2.2 None as filter. This resets the default behaviour. +### 2.2 None as filter. This resets the default behavior. with_test_prefix "None" { gdb_test_multiline "register filter in python" \ "python" "" \ diff --git a/gdb/testsuite/gdb.cp/empty-enum.exp b/gdb/testsuite/gdb.cp/empty-enum.exp index 6acae55..6816e86 100644 --- a/gdb/testsuite/gdb.cp/empty-enum.exp +++ b/gdb/testsuite/gdb.cp/empty-enum.exp @@ -25,7 +25,7 @@ # (gdb) print enum_var # $1 = 8 # -# This test checks this behaviour. +# This test checks this behavior. standard_testfile .cc diff --git a/gdb/testsuite/gdb.cp/gdb2495.exp b/gdb/testsuite/gdb.cp/gdb2495.exp index 7fbadb2..86ee7f9 100644 --- a/gdb/testsuite/gdb.cp/gdb2495.exp +++ b/gdb/testsuite/gdb.cp/gdb2495.exp @@ -24,7 +24,7 @@ # in-frame). The default handler calls std::terminate. This will kill # the inferior. Assert that terminate should never be called in an # inferior function call. These tests test the functionality around -# unwinding that sequence and also tests the flag behaviour gating this +# unwinding that sequence and also tests the flag behavior gating this # functionality. # # PR c++/9600. @@ -51,7 +51,7 @@ if {![runto_main]} { # See http://sourceware.org/gdb/bugs/2495 -# Test normal baseline behaviour. Call a function that +# Test normal baseline behavior. Call a function that # does not raise an exception. gdb_test "p exceptions.no_throw_function()" " = 1" # And one that does but handles it in-frame. @@ -75,7 +75,7 @@ gdb_test "bt" \ gdb_test "info breakpoints" \ "gdb2495\.cc.*" -# Turn off this new behaviour. +# Turn off this new behavior. gdb_test_no_output "set unwind-on-terminating-exception off" # Check that it is turned off. @@ -83,7 +83,7 @@ gdb_test "show unwind-on-terminating-exception" \ "exception is unhandled while in a call dummy is off.*" \ "turn off unwind on terminating exception flag" -# Check that the old behaviour is restored. +# Check that the old behavior is restored. gdb_test "p exceptions.throw_function()" \ "The program being debugged was signaled while in a function called .*" \ "call a function that raises an exception with unwinding off.." @@ -94,10 +94,10 @@ if {![runto_main]} { } -# Check to see if the new behaviour alters the unwind signal +# Check to see if the new behavior alters the unwind signal # behaviour; it should not. Test both on and off states. -# Turn on unwind on signal behaviour. +# Turn on unwind on signal behavior. gdb_test_no_output "set unwind-on-signal on" # Check that it is turned on. @@ -105,7 +105,7 @@ gdb_test "show unwind-on-signal" \ "signal is received while in a call dummy is on.*" \ "turn on unwind on signal" -# Check to see if new behaviour interferes with +# Check to see if new behavior interferes with # normal signal handling in inferior function calls. gdb_test "p exceptions.raise_signal(1)" \ [multi_line \ @@ -124,7 +124,7 @@ gdb_test "show unwind-on-signal" \ "signal is received while in a call dummy is off.*" \ "turn off unwind on signal" -# Check to see if new behaviour interferes with +# Check to see if new behavior interferes with # normal signal handling in inferior function calls. gdb_test "p exceptions.raise_signal(1)" \ "To change this behavior use \"set unwind-on-signal on\".*" \ diff --git a/gdb/testsuite/gdb.debuginfod/corefile-mapped-file-3.c b/gdb/testsuite/gdb.debuginfod/corefile-mapped-file-3.c index 98ed952..e060866 100644 --- a/gdb/testsuite/gdb.debuginfod/corefile-mapped-file-3.c +++ b/gdb/testsuite/gdb.debuginfod/corefile-mapped-file-3.c @@ -38,7 +38,7 @@ main () library_base_address = mmap (NULL, buf.st_size, PROT_READ, MAP_PRIVATE, fd, 0); - res = *ptr; /* Undefined behaviour here. */ + res = *ptr; /* Undefined behavior here. */ return 0; } diff --git a/gdb/testsuite/gdb.debuginfod/corefile-mapped-file.exp b/gdb/testsuite/gdb.debuginfod/corefile-mapped-file.exp index cad70aa..f02876e 100644 --- a/gdb/testsuite/gdb.debuginfod/corefile-mapped-file.exp +++ b/gdb/testsuite/gdb.debuginfod/corefile-mapped-file.exp @@ -169,7 +169,7 @@ if {![runto_main]} { return } -gdb_breakpoint [gdb_get_line_number "Undefined behaviour here" $srcfile3] +gdb_breakpoint [gdb_get_line_number "Undefined behavior here" $srcfile3] gdb_continue_to_breakpoint "run to breakpoint" set library_base_address \ diff --git a/gdb/testsuite/gdb.dlang/expression.exp b/gdb/testsuite/gdb.dlang/expression.exp index 8f72ec0..c3b8bd2 100644 --- a/gdb/testsuite/gdb.dlang/expression.exp +++ b/gdb/testsuite/gdb.dlang/expression.exp @@ -107,7 +107,7 @@ proc test_d_float_literals {} { } proc test_d_expressions {} { - # Test expression behaviour specific to D. + # Test expression behavior specific to D. # Comparison and order expressions have same precedence. gdb_test "print 1 == 2 > 0" "A syntax error in expression, near `> 0'\." diff --git a/gdb/testsuite/gdb.dwarf2/dw2-inline-header-2.exp b/gdb/testsuite/gdb.dwarf2/dw2-inline-header-2.exp index 68f1fc8..4fd4c5a 100644 --- a/gdb/testsuite/gdb.dwarf2/dw2-inline-header-2.exp +++ b/gdb/testsuite/gdb.dwarf2/dw2-inline-header-2.exp @@ -34,7 +34,7 @@ # third breakpoint will actually be placed at the same location as the # second breakpoint. # -# This test is designed to test GDB's internal behaviour with respect +# This test is designed to test GDB's internal behavior with respect # to discarding particular line table entries. GCC and DWARF are # starting to introduce the idea of line table views. As the views # information becomes better supported within GDB it is likely that diff --git a/gdb/testsuite/gdb.dwarf2/dw2-inline-stepping.c b/gdb/testsuite/gdb.dwarf2/dw2-inline-stepping.c index 6b0e7ac..109a372 100644 --- a/gdb/testsuite/gdb.dwarf2/dw2-inline-stepping.c +++ b/gdb/testsuite/gdb.dwarf2/dw2-inline-stepping.c @@ -14,7 +14,7 @@ along with this program. If not, see <http://www.gnu.org/licenses/>. */ /* This test relies on foo being inlined into main and bar not being - inlined. The test is checking GDB's behaviour as we single step from + inlined. The test is checking GDB's behavior as we single step from main through foo and into bar. */ volatile int global_var; diff --git a/gdb/testsuite/gdb.dwarf2/dw2-missing-cu-tag.exp b/gdb/testsuite/gdb.dwarf2/dw2-missing-cu-tag.exp index f84142a..6206fb3 100644 --- a/gdb/testsuite/gdb.dwarf2/dw2-missing-cu-tag.exp +++ b/gdb/testsuite/gdb.dwarf2/dw2-missing-cu-tag.exp @@ -52,7 +52,7 @@ clean_restart gdb_test_no_output "maint set dwarf synchronous on" # This pattern is hit when GDB does not use -readnow (i.e. the default -# behaviour). +# behavior). set pattern1 \ [multi_line \ "Reading symbols from \[^\r\n\]+" \ diff --git a/gdb/testsuite/gdb.dwarf2/dw2-op-out-param.S b/gdb/testsuite/gdb.dwarf2/dw2-op-out-param.S index 0be29ff..a271dbc 100644 --- a/gdb/testsuite/gdb.dwarf2/dw2-op-out-param.S +++ b/gdb/testsuite/gdb.dwarf2/dw2-op-out-param.S @@ -16,7 +16,7 @@ along with this program. If not, see <http://www.gnu.org/licenses/>. */ -/* Test the behaviour of gdb in the following situation, the dwarf debug +/* Test the behavior of gdb in the following situation, the dwarf debug information describes a parameter as being in a register but a more recent (inner) frame marks the register as being undefined. @@ -46,7 +46,7 @@ clobbering them. The dwarf register numbering is different to the gdb register number. - In some of the tests we rely on gdb behaviour of being able to specify a + In some of the tests we rely on gdb behavior of being able to specify a struct using a single register location, the structure will then "flow" into the next gdb register. The initial register is specified using a dwarf register number, but the "next" register will depend on gdb diff --git a/gdb/testsuite/gdb.dwarf2/dw2-using-debug-str.exp b/gdb/testsuite/gdb.dwarf2/dw2-using-debug-str.exp index c84a530..762ff02 100644 --- a/gdb/testsuite/gdb.dwarf2/dw2-using-debug-str.exp +++ b/gdb/testsuite/gdb.dwarf2/dw2-using-debug-str.exp @@ -134,7 +134,7 @@ set line1 "Reading symbols from \[^\r\n\]+" set dwarf_error "DWARF Error: DW_FORM_strp used without required section" # This pattern is hit when GDB does not use -readnow (i.e. the default -# behaviour). +# behavior). set pattern1 \ [multi_line \ $line1 \ diff --git a/gdb/testsuite/gdb.fortran/array-slices.exp b/gdb/testsuite/gdb.fortran/array-slices.exp index 919a2c6..1fa6a5d 100644 --- a/gdb/testsuite/gdb.fortran/array-slices.exp +++ b/gdb/testsuite/gdb.fortran/array-slices.exp @@ -245,7 +245,7 @@ proc run_test { repack } { # The goal here is to compare the sizes of the slice in show with # the size of the slice extracted by GDB. So we can only compare # sizes when GDB's repacking setting matches the repacking - # behaviour we got from the compiler. + # behavior we got from the compiler. if { ($addr_in_show < $start_addr || $addr_in_show >= $end_addr) \ == ($repack == "on") } { gdb_assert {$size_in_show == $size_in_parent} \ diff --git a/gdb/testsuite/gdb.fortran/nested-funcs-2.exp b/gdb/testsuite/gdb.fortran/nested-funcs-2.exp index 6af9cd6..72d87bc 100644 --- a/gdb/testsuite/gdb.fortran/nested-funcs-2.exp +++ b/gdb/testsuite/gdb.fortran/nested-funcs-2.exp @@ -90,7 +90,7 @@ proc do_bp_tests {with_src_prefix_p with_nest_prefix_p} { # Currently referencing symbols using 'info', # 'whatis' and 'ptype' before the program is # started doesn't work. This is the same - # behaviour we see in C++ so I don't think this + # behavior we see in C++ so I don't think this # is a failure, just a limitation in current GDB. if { ${with_nest_prefix_p} } { gdb_test "info symbol ${nest_prefix}${function}" \ diff --git a/gdb/testsuite/gdb.mi/mi-condbreak-throw.exp b/gdb/testsuite/gdb.mi/mi-condbreak-throw.exp index e35ad8f..2d2392d 100644 --- a/gdb/testsuite/gdb.mi/mi-condbreak-throw.exp +++ b/gdb/testsuite/gdb.mi/mi-condbreak-throw.exp @@ -75,7 +75,7 @@ proc run_test { unwind_on_exception } { "&\"caused by an unhandled C\\+\\+ exception. GDB blocked this call in order\\\\n\"" \ "&\"to prevent the program from being terminated, and has restored the\\\\n\"" \ "&\"context to its original state before the call.\\\\n\"" \ - "&\"To change this behaviour use \\\\\"set unwind-on-terminating-exception off\\\\\"\\.\\\\n\"" \ + "&\"To change this behavior use \\\\\"set unwind-on-terminating-exception off\\\\\"\\.\\\\n\"" \ "&\"Evaluation of the expression containing the function \\(cond_throw\\(\\)\\)\\\\n\"" \ "&\"will be abandoned.\\\\n\"" \ "=breakpoint-modified,bkpt={number=\"$bpnum\",type=\"breakpoint\",\[^\r\n\]+times=\"1\",\[^\r\n\]+}" \ diff --git a/gdb/testsuite/gdb.mi/mi-vla-fortran.exp b/gdb/testsuite/gdb.mi/mi-vla-fortran.exp index 6097c02..d0b4a22 100644 --- a/gdb/testsuite/gdb.mi/mi-vla-fortran.exp +++ b/gdb/testsuite/gdb.mi/mi-vla-fortran.exp @@ -158,7 +158,7 @@ gdb_expect { "$real" "get children of pvla2_not_associated" } -re "580\\^error,msg=\"value contents too large \\(\[0-9\]+ bytes\\).*${mi_gdb_prompt}$" { - # Undefined behaviour in gfortran. + # Undefined behavior in gfortran. xfail $test } -re "${mi_gdb_prompt}$" { diff --git a/gdb/testsuite/gdb.server/non-existing-program.exp b/gdb/testsuite/gdb.server/non-existing-program.exp index 2d08e50..71b29c2 100644 --- a/gdb/testsuite/gdb.server/non-existing-program.exp +++ b/gdb/testsuite/gdb.server/non-existing-program.exp @@ -45,7 +45,7 @@ expect { exp_continue } # Likewise, but with startup-with-shell enabled, which is the - # default behaviour. + # default behavior. -re "stdin/stdout redirected.*exec: non-existing-program: not found\r\nDuring startup program exited with code 127\.\r\nExiting\r\n" { set saw_exiting 1 exp_continue diff --git a/gdb/testsuite/gdb.server/target-exec-file.exp b/gdb/testsuite/gdb.server/target-exec-file.exp index 91e4c5c..9a24b7a 100644 --- a/gdb/testsuite/gdb.server/target-exec-file.exp +++ b/gdb/testsuite/gdb.server/target-exec-file.exp @@ -189,7 +189,7 @@ proc start_inferior { testname expect_reread } { } gdb_assert { $expect_reread == $saw_reread } \ - "check symbol re-read behaviour" + "check symbol re-read behavior" } } 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 diff --git a/gdb/testsuite/lib/read1.c b/gdb/testsuite/lib/read1.c index e449717..29570c9 100644 --- a/gdb/testsuite/lib/read1.c +++ b/gdb/testsuite/lib/read1.c @@ -62,7 +62,7 @@ init_readmore (int *method, unsigned int *sleep, FILE **log) *log = fopen (env, "w"); } -/* Wrap 'read', and modify it's behaviour using READ1 or READMORE style. */ +/* Wrap 'read', and modify it's behavior using READ1 or READMORE style. */ ssize_t read (int fd, void *buf, size_t count) @@ -89,7 +89,7 @@ read (int fd, void *buf, size_t count) init_readmore (&readmore_method, &readmore_sleep, &log); } - /* Only modify 'read' behaviour when reading from the terminal. */ + /* Only modify 'read' behavior when reading from the terminal. */ if (isatty (fd) == 0) goto fallback; |