From patchwork Fri Nov 25 19:46:34 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Ambrogino Modigliani X-Patchwork-Id: 17933 Received: (qmail 35474 invoked by alias); 25 Nov 2016 19:47:52 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Delivered-To: mailing list gdb-patches@sourceware.org Received: (qmail 34027 invoked by uid 89); 25 Nov 2016 19:47:35 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.1 required=5.0 tests=AWL, BAYES_50, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, RCVD_IN_SORBS_SPAM, SPF_PASS autolearn=no version=3.3.2 spammy=privileges, TWO, substantial, watched X-HELO: mail-wm0-f65.google.com Received: from mail-wm0-f65.google.com (HELO mail-wm0-f65.google.com) (74.125.82.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 25 Nov 2016 19:47:17 +0000 Received: by mail-wm0-f65.google.com with SMTP id g23so9191549wme.1 for ; Fri, 25 Nov 2016 11:47:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:date:message-id:in-reply-to :references; bh=++1+pGFyikGOfH8YotnXKboLDTNrv05e7lN02HOMiUI=; b=j41CyLfuujfJOtlqacpB9B21TRAqgTKRwcj8z+e6Z9msrc7opEGmrPK7eYXK8QtO64 3wzX6PRlaIT3aC692iKamLi2gGs/cftIqlMHZlUBC15SimN4nACqEHlLeCbonuYIBa2h cn6q/3nhStJZNSeBwDCtMiZ9HKbPBycaIkqsMWgbBYwYfHwYehsYz3O7zT1Iskecp1eu Rg+4WdHZaTYUoihhPLG4BWLSDPl7raztRd2wsO4bLvtH8R37zhIDr3IIvKY7VJOrYn+G OKXT43Fu4z2hNLeASiaaz8Oh4IZq72LG3fQFgTVMYg6oddbpTfLk7GIzLQKcWsnMpac/ p3+A== X-Gm-Message-State: AKaTC013uiAPlIdUZGR7R+gbBqRUbTPELZndDwKfcE+xUvktING/NhIFNjSKHHymAr4Vdw== X-Received: by 10.28.135.5 with SMTP id j5mr9728150wmd.3.1480103233722; Fri, 25 Nov 2016 11:47:13 -0800 (PST) Received: from localhost.localdomain ([95.180.71.38]) by smtp.googlemail.com with ESMTPSA id l67sm14208774wmf.0.2016.11.25.11.47.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 25 Nov 2016 11:47:12 -0800 (PST) From: Ambrogino Modigliani X-Google-Original-From: Ambrogino Modigliani To: gdb-patches@sourceware.org, pedro_alves@portugalmail.pt, ambrogino.modigliani@gmail.com, ambrogino.modigliani@mail.com Subject: [PATCH 08/17] Fix spelling in comments in Expect scripts (gdb) Date: Fri, 25 Nov 2016 20:46:34 +0100 Message-Id: <1480103203-9710-9-git-send-email-ambrogino.modigliani@mail.com> In-Reply-To: <1480103203-9710-1-git-send-email-ambrogino.modigliani@mail.com> References: <1480103203-9710-1-git-send-email-ambrogino.modigliani@mail.com> gdb/testsuite/ChangeLog: * gdb.ada/exec_changed.exp: Fix spelling in comments. * gdb.arch/e500-prologue.exp: Fix spelling in comments. * gdb.arch/i386-mpx.exp: Fix spelling in comments. * gdb.arch/powerpc-aix-prologue.exp: Fix spelling in comments. * gdb.base/bigcore.exp: Fix spelling in comments. * gdb.base/call-sc.exp: Fix spelling in comments. * gdb.base/dbx.exp: Fix spelling in comments. * gdb.base/default.exp: Fix spelling in comments. * gdb.base/double-prompt-target-event-error.exp: Fix spelling in comments. * gdb.base/exitsignal.exp: Fix spelling in comments. * gdb.base/gdb11531.exp: Fix spelling in comments. * gdb.base/gnu-ifunc.exp: Fix spelling in comments. * gdb.base/gnu_vector.exp: Fix spelling in comments. * gdb.base/lineinc.exp: Fix spelling in comments. * gdb.base/killed-outside.exp: Fix spelling in comments. * gdb.base/overlays.exp: Fix spelling in comments. * gdb.base/remote.exp: Fix spelling in comments. * gdb.base/savedregs.exp: Fix spelling in comments. * gdb.base/scope.exp: Fix spelling in comments. * gdb.base/sigbpt.exp: Fix spelling in comments. * gdb.base/signals.exp: Fix spelling in comments. * gdb.base/signull.exp: Fix spelling in comments. * gdb.base/store.exp: Fix spelling in comments. * gdb.base/structs.exp: Fix spelling in comments. * gdb.base/watchpoint-stops-at-right-insn.exp: Fix spelling in comments. * gdb.cell/mem-access.exp: Fix spelling in comments. * gdb.cp/rtti.exp: Fix spelling in comments. * gdb.cp/static-print-quit.exp: Fix spelling in comments. * gdb.cp/virtfunc.exp: Fix spelling in comments. * gdb.dwarf2/dw2-ranges-base.exp: Fix spelling in comments. * gdb.fortran/types.exp: Fix spelling in comments. * gdb.fortran/vla-value-sub-arbitrary.exp: Fix spelling in comments. * gdb.go/integers.exp: Fix spelling in comments. * gdb.mi/mi-breakpoint-changed.exp: Fix spelling in comments. * gdb.multi/multi-arch-exec.exp: Fix spelling in comments. * gdb.pascal/floats.exp: Fix spelling in comments. * gdb.pascal/integers.exp: Fix spelling in comments. * gdb.pascal/types.exp: Fix spelling in comments. * gdb.reverse/step-precsave.exp: Fix spelling in comments. * gdb.reverse/step-reverse.exp: Fix spelling in comments. * gdb.threads/thread_check.exp: Fix spelling in comments. * gdb.trace/collection.exp: Fix spelling in comments. * gdb.trace/mi-tracepoint-changed.exp: Fix spelling in comments. * lib/gdb.exp: Fix spelling in comments. * lib/prelink-support.exp: Fix spelling in comments. --- gdb/testsuite/gdb.ada/exec_changed.exp | 2 +- gdb/testsuite/gdb.arch/e500-prologue.exp | 2 +- gdb/testsuite/gdb.arch/i386-mpx.exp | 2 +- gdb/testsuite/gdb.arch/powerpc-aix-prologue.exp | 2 +- gdb/testsuite/gdb.base/bigcore.exp | 2 +- gdb/testsuite/gdb.base/call-sc.exp | 6 +++--- gdb/testsuite/gdb.base/dbx.exp | 2 +- gdb/testsuite/gdb.base/default.exp | 2 +- gdb/testsuite/gdb.base/double-prompt-target-event-error.exp | 4 ++-- gdb/testsuite/gdb.base/exitsignal.exp | 2 +- gdb/testsuite/gdb.base/gdb11531.exp | 2 +- gdb/testsuite/gdb.base/gnu-ifunc.exp | 2 +- gdb/testsuite/gdb.base/gnu_vector.exp | 2 +- gdb/testsuite/gdb.base/killed-outside.exp | 2 +- gdb/testsuite/gdb.base/lineinc.exp | 2 +- gdb/testsuite/gdb.base/overlays.exp | 2 +- gdb/testsuite/gdb.base/remote.exp | 6 +++--- gdb/testsuite/gdb.base/savedregs.exp | 2 +- gdb/testsuite/gdb.base/scope.exp | 2 +- gdb/testsuite/gdb.base/sigbpt.exp | 2 +- gdb/testsuite/gdb.base/signals.exp | 2 +- gdb/testsuite/gdb.base/signull.exp | 2 +- gdb/testsuite/gdb.base/store.exp | 2 +- gdb/testsuite/gdb.base/structs.exp | 6 +++--- gdb/testsuite/gdb.base/watchpoint-stops-at-right-insn.exp | 2 +- gdb/testsuite/gdb.cell/mem-access.exp | 6 +++--- gdb/testsuite/gdb.cp/rtti.exp | 2 +- gdb/testsuite/gdb.cp/static-print-quit.exp | 2 +- gdb/testsuite/gdb.cp/virtfunc.exp | 2 +- gdb/testsuite/gdb.dwarf2/dw2-ranges-base.exp | 2 +- gdb/testsuite/gdb.fortran/types.exp | 2 +- gdb/testsuite/gdb.fortran/vla-value-sub-arbitrary.exp | 2 +- gdb/testsuite/gdb.go/integers.exp | 2 +- gdb/testsuite/gdb.mi/mi-breakpoint-changed.exp | 2 +- gdb/testsuite/gdb.multi/multi-arch-exec.exp | 2 +- gdb/testsuite/gdb.pascal/floats.exp | 2 +- gdb/testsuite/gdb.pascal/integers.exp | 2 +- gdb/testsuite/gdb.pascal/types.exp | 2 +- gdb/testsuite/gdb.reverse/step-precsave.exp | 8 ++++---- gdb/testsuite/gdb.reverse/step-reverse.exp | 8 ++++---- gdb/testsuite/gdb.threads/thread_check.exp | 2 +- gdb/testsuite/gdb.trace/collection.exp | 4 ++-- gdb/testsuite/gdb.trace/mi-tracepoint-changed.exp | 2 +- gdb/testsuite/lib/gdb.exp | 8 ++++---- gdb/testsuite/lib/prelink-support.exp | 4 ++-- 45 files changed, 65 insertions(+), 65 deletions(-) diff --git a/gdb/testsuite/gdb.ada/exec_changed.exp b/gdb/testsuite/gdb.ada/exec_changed.exp index a574cd5..06e1c2a 100644 --- a/gdb/testsuite/gdb.ada/exec_changed.exp +++ b/gdb/testsuite/gdb.ada/exec_changed.exp @@ -85,7 +85,7 @@ if { [gdb_start_cmd] < 0 } { clean_restart "${binfile}$EXEEXT" -# Ensure we don't accidently use the main symbol cache. +# Ensure we don't accidentally use the main symbol cache. gdb_test_no_output "mt set symbol-cache-size 0" # Put something in the symbol lookup cache that will get looked up when diff --git a/gdb/testsuite/gdb.arch/e500-prologue.exp b/gdb/testsuite/gdb.arch/e500-prologue.exp index 3019b3e..7084ea1 100644 --- a/gdb/testsuite/gdb.arch/e500-prologue.exp +++ b/gdb/testsuite/gdb.arch/e500-prologue.exp @@ -60,7 +60,7 @@ proc insert_breakpoint {function expected_location} { # If we managed to get the breakpoing address, then check that # we inserted it at the expected location by examining the # instruction at that address (we're not interested in the insn - # itself, but rather at the address printed at the begining of + # itself, but rather at the address printed at the beginning of # the instruction). if { $address != "" } then { gdb_test "x /i $address" \ diff --git a/gdb/testsuite/gdb.arch/i386-mpx.exp b/gdb/testsuite/gdb.arch/i386-mpx.exp index 7f4727e..a0610b1 100644 --- a/gdb/testsuite/gdb.arch/i386-mpx.exp +++ b/gdb/testsuite/gdb.arch/i386-mpx.exp @@ -138,7 +138,7 @@ gdb_test "print /x \$bnd0raw" "$test_string" "bnd0raw after setting full bnd0" gdb_test "print \$bndstatus.status.error" "= 2" "bndstatus error is 2\ after a failure on allocating an entry" -# Going to test the python extension for lenght. +# Going to test the python extension for length. if { [skip_python_tests] } { continue } # Verify if size is right set test_string ".*\\\: size 17.*" diff --git a/gdb/testsuite/gdb.arch/powerpc-aix-prologue.exp b/gdb/testsuite/gdb.arch/powerpc-aix-prologue.exp index d82c4de..e0975e4 100644 --- a/gdb/testsuite/gdb.arch/powerpc-aix-prologue.exp +++ b/gdb/testsuite/gdb.arch/powerpc-aix-prologue.exp @@ -60,7 +60,7 @@ proc insert_breakpoint {function expected_location} { # If we managed to get the breakpoing address, then check that # we inserted it at the expected location by examining the # instruction at that address (we're not interested in the insn - # itself, but rather at the address printed at the begining of + # itself, but rather at the address printed at the beginning of # the instruction). if { $address != "" } then { gdb_test "x /i $address" \ diff --git a/gdb/testsuite/gdb.base/bigcore.exp b/gdb/testsuite/gdb.base/bigcore.exp index ae00d0a..441b2ef 100644 --- a/gdb/testsuite/gdb.base/bigcore.exp +++ b/gdb/testsuite/gdb.base/bigcore.exp @@ -28,7 +28,7 @@ if ![isnative] then { # 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 89065e1..28ed6bd 100644 --- a/gdb/testsuite/gdb.base/call-sc.exp +++ b/gdb/testsuite/gdb.base/call-sc.exp @@ -177,7 +177,7 @@ proc test_scalar_returns { } { # Check that "return" works. # GDB must always force the return of a function that has - # a struct result. Dependant on the ABI, it may, or may not be + # a struct result. Dependent on the ABI, it may, or may not be # possible to store the return value in a register. # The relevant code looks like "L{n} = fun{n}()". The test forces @@ -202,7 +202,7 @@ proc test_scalar_returns { } { # known, both failed to print a final "source and line" and misplaced # the frame ("No frame"). - # The test is writen so that it only reports one FAIL/PASS for the + # The test is written so that it only reports one FAIL/PASS for the # entire operation. The value returned is checked further down. # "return_value_unknown", if non-empty, records why GDB realised # that it didn't know where the return value was. @@ -291,7 +291,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/dbx.exp b/gdb/testsuite/gdb.base/dbx.exp index 3d18d6f..e9f3a4d 100644 --- a/gdb/testsuite/gdb.base/dbx.exp +++ b/gdb/testsuite/gdb.base/dbx.exp @@ -129,7 +129,7 @@ proc dbx_reinitialize_dir { subdir } { # as a side effect of running a particular test (in this case, # "testsuite/gdb.compat/dbx.exp"). # -# CM: Renamed the procedure so it does not override the orginal file name. +# CM: Renamed the procedure so it does not override the original file name. # Having the test suite change behavior depending on the tests run makes # it extremely difficult to reproduce errors. I've also added a # "dbx_gdb_load" procedure. This and only this test will call these diff --git a/gdb/testsuite/gdb.base/default.exp b/gdb/testsuite/gdb.base/default.exp index c5a9072..70aba4f 100644 --- a/gdb/testsuite/gdb.base/default.exp +++ b/gdb/testsuite/gdb.base/default.exp @@ -455,7 +455,7 @@ gdb_test "rbreak" "rbreak" gdb_test "restore" "You can't do that without a process to debug\." #test return -# The middle case accomodated the obsolete a29k, where doing the "ni" +# The middle case accommodated the obsolete a29k, where doing the "ni" # above causes an initial stack to be created. gdb_test "return" "No selected frame..*" "return" "Make .* return now.*y or n. $" "y" diff --git a/gdb/testsuite/gdb.base/double-prompt-target-event-error.exp b/gdb/testsuite/gdb.base/double-prompt-target-event-error.exp index ebf2231..229f8ee 100644 --- a/gdb/testsuite/gdb.base/double-prompt-target-event-error.exp +++ b/gdb/testsuite/gdb.base/double-prompt-target-event-error.exp @@ -54,7 +54,7 @@ proc cancel_pagination_in_target_event { command } { if { $command == "wrapcont" } { gdb_test_multiple "define wrapcont" "define user command: wrapcont" { -re "Type commands for definition of \"wrapcont\".\r\nEnd with a line saying just \"end\".\r\n>$" { - # Note that "Continuing." is ommitted when + # Note that "Continuing." is omitted when # "continue" is issued from a user-defined # command. Issue it ourselves. gdb_test "echo Continuing\.\ncontinue\nend" "" \ @@ -98,7 +98,7 @@ proc cancel_pagination_in_target_event { command } { } # We should only see one prompt more, and it should be - # preceeded by print's output. + # preceded by print's output. set test "no double prompt" gdb_test_multiple "" $test { -re "$gdb_prompt.*$gdb_prompt $" { diff --git a/gdb/testsuite/gdb.base/exitsignal.exp b/gdb/testsuite/gdb.base/exitsignal.exp index d7027d3..d4149a2 100644 --- a/gdb/testsuite/gdb.base/exitsignal.exp +++ b/gdb/testsuite/gdb.base/exitsignal.exp @@ -17,7 +17,7 @@ # purpose of this checking is to ensure that the variables are # mutually exclusive, i.e., that when $_exitsignal is set, $_exitcode # is not, and vice-versa. This mutual exclusion happens because if an -# inferior exited (either successfuly or not), it certainly was not +# inferior exited (either successfully or not), it certainly was not # killed by a signal. However, if it was killed by an uncaught # signal, then there is no way for it to have exited. diff --git a/gdb/testsuite/gdb.base/gdb11531.exp b/gdb/testsuite/gdb.base/gdb11531.exp index 3ed5a0b..fa2d1b5 100644 --- a/gdb/testsuite/gdb.base/gdb11531.exp +++ b/gdb/testsuite/gdb.base/gdb11531.exp @@ -40,7 +40,7 @@ if { ![runto main] } then { # watched (myrec.x) gets updated. This is the instruction where we # expect to receive a watchpoint notification when we do the "stepi" # below. However, having the breakpoint at the same location as this -# intruction can possibly interfere with our testcase, as stepping +# instruction can possibly interfere with our testcase, as stepping # over the breakpoint in order to get past it may incorrectly lead # to the debugger missing the watchpoint hit. This would be a bug # in GDB, but this is not the bug that we are trying to test here. diff --git a/gdb/testsuite/gdb.base/gnu-ifunc.exp b/gdb/testsuite/gdb.base/gnu-ifunc.exp index 3b2775b..a430817 100644 --- a/gdb/testsuite/gdb.base/gnu-ifunc.exp +++ b/gdb/testsuite/gdb.base/gnu-ifunc.exp @@ -66,7 +66,7 @@ if ![runto_main] then { return 1 } -# The "if" condition is artifical to test regression of a former patch. +# The "if" condition is artificial to test regression of a former patch. gdb_breakpoint "[gdb_get_line_number "break-at-nextcall"] if i && gnu_ifunc (i) != 42" gdb_breakpoint [gdb_get_line_number "break-at-call"] diff --git a/gdb/testsuite/gdb.base/gnu_vector.exp b/gdb/testsuite/gdb.base/gnu_vector.exp index aafaedd..fe76933 100644 --- a/gdb/testsuite/gdb.base/gnu_vector.exp +++ b/gdb/testsuite/gdb.base/gnu_vector.exp @@ -47,7 +47,7 @@ if { ![runto main] } { return -1 } -# Get endianess for the scalar->vector casts +# Get endianness for the scalar->vector casts gdb_test_multiple "show endian" "show endian" { -re ".* (big|little) endian.*$gdb_prompt $" { set endian $expect_out(1,string) diff --git a/gdb/testsuite/gdb.base/killed-outside.exp b/gdb/testsuite/gdb.base/killed-outside.exp index 2720052..6ab2886 100644 --- a/gdb/testsuite/gdb.base/killed-outside.exp +++ b/gdb/testsuite/gdb.base/killed-outside.exp @@ -102,7 +102,7 @@ with_test_prefix "continue" { } } -# Try stepping the program. Stepping may go through diferent code +# Try stepping the program. Stepping may go through different code # paths in the target backends. with_test_prefix "stepi" { test { diff --git a/gdb/testsuite/gdb.base/lineinc.exp b/gdb/testsuite/gdb.base/lineinc.exp index 4070f4e..5e7ca0d 100644 --- a/gdb/testsuite/gdb.base/lineinc.exp +++ b/gdb/testsuite/gdb.base/lineinc.exp @@ -70,7 +70,7 @@ # #included by a given source file in a list sorted by the line at # which they were #included; this gives GDB the chance to detect # multiple #inclusions at the same line, complain, and assign -# distinct, albiet incorrect, line numbers to each #inclusion. +# distinct, albeit incorrect, line numbers to each #inclusion. # # However, at one point GDB was sorting the list in reverse order, # while the code to assign new, distinct line numbers assumed it was diff --git a/gdb/testsuite/gdb.base/overlays.exp b/gdb/testsuite/gdb.base/overlays.exp index cf4213a..dd92351 100644 --- a/gdb/testsuite/gdb.base/overlays.exp +++ b/gdb/testsuite/gdb.base/overlays.exp @@ -163,7 +163,7 @@ if $data_overlays then { } # Verify that early-mapped overlays have been bumped out -# by later-mapped overlays layed over in the same VMA range. +# by later-mapped overlays laid over in the same VMA range. send_gdb "overlay list\n" gdb_expect { diff --git a/gdb/testsuite/gdb.base/remote.exp b/gdb/testsuite/gdb.base/remote.exp index a3c34eb..3d11790 100644 --- a/gdb/testsuite/gdb.base/remote.exp +++ b/gdb/testsuite/gdb.base/remote.exp @@ -32,7 +32,7 @@ if {$result != "" } then { # -# Part ONE: Check the down load commands +# Part ONE: Check the download commands # gdb_test "show remote memory-write-packet-size" \ @@ -54,7 +54,7 @@ gdb_test "show remote memory-write-packet-size" \ "set write-packet - very-small" # -# Part TWO: Check the download behavour +# Part TWO: Check the download behavior # proc gdb_load_timed {executable class writesize} { @@ -124,7 +124,7 @@ gdb_load_timed $binfile "limit" 0 set sizeof_random_data [get_sizeof "random_data" 48*1024] # -# Part THREE: Check the upload behavour +# Part THREE: Check the upload behavior # if ![runto_main] then { fail "Cannot run to main" diff --git a/gdb/testsuite/gdb.base/savedregs.exp b/gdb/testsuite/gdb.base/savedregs.exp index eea30d1..cab5ec1 100644 --- a/gdb/testsuite/gdb.base/savedregs.exp +++ b/gdb/testsuite/gdb.base/savedregs.exp @@ -60,7 +60,7 @@ proc process_saved_regs { current inner outer } { # and for dummy frames won't have saved registers. If there's a # problem, fail but capture the output anyway, hopefully later # "info frame" requests for that same frame will at least fail in - # a consistent manner (stops propogated fails). + # a consistent manner (stops propagated fails). foreach func $inner { set saved_regs($func) "error" diff --git a/gdb/testsuite/gdb.base/scope.exp b/gdb/testsuite/gdb.base/scope.exp index 37d0657..5f2d960 100644 --- a/gdb/testsuite/gdb.base/scope.exp +++ b/gdb/testsuite/gdb.base/scope.exp @@ -511,7 +511,7 @@ gdb_test "print 'scope0.c'::filelocal_ro" "= 201" # For PA boards using monitor/remote-pa.c, the bss test is going to # randomly fail. We've already put remote-pa on the target stack, # so we actually read memory from the board. Problem is crt0.o -# is responsible for clearing bss and that hasnt' happened yet. +# is responsible for clearing bss and that hasn't happened yet. # # This is a problem for all non-native targets. -- manson if [is_remote target] { diff --git a/gdb/testsuite/gdb.base/sigbpt.exp b/gdb/testsuite/gdb.base/sigbpt.exp index d291c97..8a1c638 100644 --- a/gdb/testsuite/gdb.base/sigbpt.exp +++ b/gdb/testsuite/gdb.base/sigbpt.exp @@ -22,7 +22,7 @@ # This test is known to tickle the following problems: kernel letting # the inferior execute both the system call, and the instruction # following, when single-stepping a system call; kernel failing to -# propogate the single-step state when single-stepping the sigreturn +# propagate the single-step state when single-stepping the sigreturn # system call, instead resuming the inferior at full speed; GDB # doesn't know how to software single-step across a sigreturn # instruction. Since the kernel problems can be "fixed" using diff --git a/gdb/testsuite/gdb.base/signals.exp b/gdb/testsuite/gdb.base/signals.exp index 677e77f..2c616bb 100644 --- a/gdb/testsuite/gdb.base/signals.exp +++ b/gdb/testsuite/gdb.base/signals.exp @@ -114,7 +114,7 @@ if [runto_main] then { "next to ++count #2" sleep 2 - # ...call the function, which is immediatly interrupted + # ...call the function, which is immediately interrupted gdb_test "p func1 ()" \ "Breakpoint \[0-9\]*, handler.* diff --git a/gdb/testsuite/gdb.base/signull.exp b/gdb/testsuite/gdb.base/signull.exp index a10c83e..c283167 100644 --- a/gdb/testsuite/gdb.base/signull.exp +++ b/gdb/testsuite/gdb.base/signull.exp @@ -93,7 +93,7 @@ gdb_test "break keeper" gdb_test "handle SIGSEGV" "SIGSEGV.*Yes.*Yes.*Yes.*Segmentation fault" gdb_test "handle SIGBUS" "SIGBUS.*Yes.*Yes.*Yes.*Bus error" -# For the given signal type, check that: the SIGSEGV occures; a +# For the given signal type, check that: the SIGSEGV occurs; a # backtrace from the SEGV works; the sigsegv is delivered; a backtrace # through the SEGV works. diff --git a/gdb/testsuite/gdb.base/store.exp b/gdb/testsuite/gdb.base/store.exp index fed5c8a..895c321 100644 --- a/gdb/testsuite/gdb.base/store.exp +++ b/gdb/testsuite/gdb.base/store.exp @@ -156,7 +156,7 @@ proc check_field { t } { gdb_test "continue" "register struct f_${t} u = f_${t};" \ "continue field ${t}" - # Match either the return statement, or the line immediatly after + # Match either the return statement, or the line immediately after # it. The compiler can end up merging the return statement into # the return instruction. gdb_test "next" "(return u;|\})" "next field ${t}" diff --git a/gdb/testsuite/gdb.base/structs.exp b/gdb/testsuite/gdb.base/structs.exp index 4fcef52..e9f4343 100644 --- a/gdb/testsuite/gdb.base/structs.exp +++ b/gdb/testsuite/gdb.base/structs.exp @@ -288,7 +288,7 @@ proc test_struct_returns { n } { # Check that "return" works. # GDB must always force the return of a function that has - # a struct result. Dependant on the ABI, it may, or may not be + # a struct result. Dependent on the ABI, it may, or may not be # possible to store the return value in a register. # The relevant code looks like "L{n} = fun{n}()". The test forces @@ -313,7 +313,7 @@ proc test_struct_returns { n } { # known, both failed to print a final "source and line" and misplaced # the frame ("No frame"). - # The test is writen so that it only reports one FAIL/PASS for the + # The test is written so that it only reports one FAIL/PASS for the # entire operation. The value returned is checked further down. # "return_value_known", if non-zero, indicates that GDB knew where # the return value was located. @@ -393,7 +393,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.base/watchpoint-stops-at-right-insn.exp b/gdb/testsuite/gdb.base/watchpoint-stops-at-right-insn.exp index 4d158c3..a90faf3 100644 --- a/gdb/testsuite/gdb.base/watchpoint-stops-at-right-insn.exp +++ b/gdb/testsuite/gdb.base/watchpoint-stops-at-right-insn.exp @@ -62,7 +62,7 @@ # # If the target has non-continuable watchpoints, while GDB thinks it # has continuable watchpoints, GDB will see a watchpoint trigger, -# notice no value changed, and immediatly continue the target. Now, +# notice no value changed, and immediately continue the target. Now, # either the target manages to step-over the watchpoint transparently, # and GDB thus fails to present to value change to the user, or, the # watchpoint will keep re-triggering, with the program never making diff --git a/gdb/testsuite/gdb.cell/mem-access.exp b/gdb/testsuite/gdb.cell/mem-access.exp index 4ba5e48..0160004 100644 --- a/gdb/testsuite/gdb.cell/mem-access.exp +++ b/gdb/testsuite/gdb.cell/mem-access.exp @@ -51,7 +51,7 @@ if [get_compiler_info] { return -1 } -# Get the adress to symbol name. If $reg +# Get the address to symbol name. If $reg # is set to 1, get address from a register. proc get_adress_from_name { name reg } { global gdb_prompt @@ -85,7 +85,7 @@ proc get_adress_from_name { name reg } { return ${adr} } -# Try to set a $value at adress $adr. +# Try to set a $value at address $adr. proc set_adr_content { adr value } { gdb_test "set *$adr=$value" \ "" \ @@ -112,7 +112,7 @@ proc test_symbol_content { symbol value } { "(symbol) $symbol==$value" } -# Check VARNAME. Check if it has the inital +# Check VARNAME. Check if it has the initial # value INITIALVALUE. Set it to NEWVALUE. # Check if set properly. Do it via symbols and # pointers. diff --git a/gdb/testsuite/gdb.cp/rtti.exp b/gdb/testsuite/gdb.cp/rtti.exp index 4969c4b..1e7e6a0 100644 --- a/gdb/testsuite/gdb.cp/rtti.exp +++ b/gdb/testsuite/gdb.cp/rtti.exp @@ -76,7 +76,7 @@ gdb_test_multiple "print *e1" "print *e1" { # NOTE: carlton/2004-01-14: This test with an "" # message because, within rtt1.cc, GDB has no way of knowing that the -# class is called 'n2::D2' instead of just 'D2'. This is an artifical +# class is called 'n2::D2' instead of just 'D2'. This is an artificial # test case, though: if we were using these classes in a more # substantial way, G++ would emit more debug info. As is, I don't # think there's anything that GDB can do about this case until G++ diff --git a/gdb/testsuite/gdb.cp/static-print-quit.exp b/gdb/testsuite/gdb.cp/static-print-quit.exp index 6157245..05a02dc 100644 --- a/gdb/testsuite/gdb.cp/static-print-quit.exp +++ b/gdb/testsuite/gdb.cp/static-print-quit.exp @@ -55,7 +55,7 @@ gdb_test_multiple "" $test { gdb_test "q" ".*" -# Now the obstack is uninitialized. Excercise it. +# Now the obstack is uninitialized. Exercise it. gdb_test_no_output "set pagination off" gdb_test "print c" ".*" "first print" diff --git a/gdb/testsuite/gdb.cp/virtfunc.exp b/gdb/testsuite/gdb.cp/virtfunc.exp index 04fe5aa..daed4a1 100644 --- a/gdb/testsuite/gdb.cp/virtfunc.exp +++ b/gdb/testsuite/gdb.cp/virtfunc.exp @@ -197,7 +197,7 @@ proc test_virtual_calls {} { # wrong value "202" # gcc 2.95.3 -gdwarf-2 # gcc 2.95.3 -gstabs+ - # attempt to take addres of value not located in memory + # attempt to take address of value not located in memory # gcc 3.3.2 -gdwarf-2 # gcc 3.3.2 -gstabs+ # diff --git a/gdb/testsuite/gdb.dwarf2/dw2-ranges-base.exp b/gdb/testsuite/gdb.dwarf2/dw2-ranges-base.exp index 3417a5c..88f5c5a 100644 --- a/gdb/testsuite/gdb.dwarf2/dw2-ranges-base.exp +++ b/gdb/testsuite/gdb.dwarf2/dw2-ranges-base.exp @@ -49,7 +49,7 @@ Dwarf::assemble $asm_file { [function_range frame3 [list ${srcdir}/${subdir}/$srcfile]] # Very simple info for this test program. We don't care about - # this information being correct (w.r.t. funtion / argument types) + # this information being correct (w.r.t. function / argument types) # just so long as the compilation using makes use of the # .debug_ranges data then the test achieves its objective. cu {} { diff --git a/gdb/testsuite/gdb.fortran/types.exp b/gdb/testsuite/gdb.fortran/types.exp index 9eb799e..e6dfb44 100644 --- a/gdb/testsuite/gdb.fortran/types.exp +++ b/gdb/testsuite/gdb.fortran/types.exp @@ -57,7 +57,7 @@ proc test_float_literal_types_accepted {} { # Test various floating point formats # this used to guess whether to look for "real*4" or - # "real*8" based on a target config variable, but noone + # "real*8" based on a target config variable, but no one # maintained it properly. gdb_test "pt .44" "type = real\\*\[0-9\]+" diff --git a/gdb/testsuite/gdb.fortran/vla-value-sub-arbitrary.exp b/gdb/testsuite/gdb.fortran/vla-value-sub-arbitrary.exp index ce33d70..a808c0b 100644 --- a/gdb/testsuite/gdb.fortran/vla-value-sub-arbitrary.exp +++ b/gdb/testsuite/gdb.fortran/vla-value-sub-arbitrary.exp @@ -25,7 +25,7 @@ if ![runto_main] { return -1 } -# Check VLA with arbitary length and check that elements outside of +# Check VLA with arbitrary length and check that elements outside of # bounds of the passed VLA can be accessed correctly. gdb_breakpoint [gdb_get_line_number "end-of-bar"] gdb_continue_to_breakpoint "end-of-bar" diff --git a/gdb/testsuite/gdb.go/integers.exp b/gdb/testsuite/gdb.go/integers.exp index b823f5a..09e447f 100644 --- a/gdb/testsuite/gdb.go/integers.exp +++ b/gdb/testsuite/gdb.go/integers.exp @@ -67,7 +67,7 @@ gdb_test "print i + k" " = 4" gdb_test "print j + k" " = 5" gdb_test "print i + j + k" " = 6" -# Test substraction +# Test subtraction gdb_test "print j - i" " = 1" gdb_test "print i - j" "= -1" gdb_test "print k -i -j" " = 0" diff --git a/gdb/testsuite/gdb.mi/mi-breakpoint-changed.exp b/gdb/testsuite/gdb.mi/mi-breakpoint-changed.exp index cda8c4a..fb76e78 100644 --- a/gdb/testsuite/gdb.mi/mi-breakpoint-changed.exp +++ b/gdb/testsuite/gdb.mi/mi-breakpoint-changed.exp @@ -157,7 +157,7 @@ with_test_prefix "test_insert_delete_modify" { test_insert_delete_modify } -# Test 'breakpoint-modified' notification is emited when pending breakpoints are +# Test 'breakpoint-modified' notification is emitted when pending breakpoints are # resolved. proc test_pending_resolved { } { diff --git a/gdb/testsuite/gdb.multi/multi-arch-exec.exp b/gdb/testsuite/gdb.multi/multi-arch-exec.exp index 88e5a62..c2e2314 100644 --- a/gdb/testsuite/gdb.multi/multi-arch-exec.exp +++ b/gdb/testsuite/gdb.multi/multi-arch-exec.exp @@ -82,6 +82,6 @@ if ![runto_main] then { return -1 } -# Test that GDB updates the target description / arch successfuly +# Test that GDB updates the target description / arch successfully # after the exec. gdb_test "continue" "Breakpoint 1, main.*" "continue across exec that changes architecture" diff --git a/gdb/testsuite/gdb.pascal/floats.exp b/gdb/testsuite/gdb.pascal/floats.exp index 43065ed..3e580e0 100644 --- a/gdb/testsuite/gdb.pascal/floats.exp +++ b/gdb/testsuite/gdb.pascal/floats.exp @@ -91,7 +91,7 @@ gdb_test "print r + (-1)" " = 0\\.2(499.*|5|500.*)" gdb_test "print r + (-5)" " = -3\\.7(499.*|5|500.*)" gdb_test "print r + (-10)" " = -8\\.7(499.*|5|500.*)" -# Test substraction +# Test subtraction gdb_test "print r - s" " = -0\\.9(499.*|5|500.*)" gdb_test "print r - t" " = 4\\.4(499.*|5|500.*)" diff --git a/gdb/testsuite/gdb.pascal/integers.exp b/gdb/testsuite/gdb.pascal/integers.exp index ec9739c..18a66fd 100644 --- a/gdb/testsuite/gdb.pascal/integers.exp +++ b/gdb/testsuite/gdb.pascal/integers.exp @@ -74,7 +74,7 @@ gdb_test "print i + k" " = 4" gdb_test "print j + k" " = 5" gdb_test "print i + j + k" " = 6" -# Test substraction +# Test subtraction gdb_test "print j - i" " = 1" gdb_test "print i - j" "= -1" gdb_test "print k -i -j" " = 0" diff --git a/gdb/testsuite/gdb.pascal/types.exp b/gdb/testsuite/gdb.pascal/types.exp index 112c612..863e3f2 100644 --- a/gdb/testsuite/gdb.pascal/types.exp +++ b/gdb/testsuite/gdb.pascal/types.exp @@ -59,7 +59,7 @@ proc test_float_literal_types_accepted {} { # Test various floating point formats # this used to guess whether to look for "real*4" or - # "real*8" based on a target config variable, but noone + # "real*8" based on a target config variable, but no one # maintained it properly. gdb_test "pt .44" "type = double" diff --git a/gdb/testsuite/gdb.reverse/step-precsave.exp b/gdb/testsuite/gdb.reverse/step-precsave.exp index 92574b6..662521e 100644 --- a/gdb/testsuite/gdb.reverse/step-precsave.exp +++ b/gdb/testsuite/gdb.reverse/step-precsave.exp @@ -135,7 +135,7 @@ gdb_test_multiple "stepi" "$test_message" { } } -# stepi thru return of a function call +# stepi through return of a function call set test_message "stepi back from function call" gdb_test_multiple "stepi" "$test_message" { @@ -167,7 +167,7 @@ gdb_test_multiple "stepi" "$test_message" { gdb_test_no_output "set exec-dir reverse" "set reverse execution" -# stepi backward thru return and into a function +# stepi backward through return and into a function set stepi_location [gdb_get_line_number "ARRIVED IN CALLEE" "$srcfile"] set test_message "reverse stepi thru function return" @@ -238,12 +238,12 @@ gdb_test_multiple "stepi" "$test_message" { } } -# step backward into function (thru return) +# step backward into function (through return) gdb_test "step" "(RETURN FROM CALLEE|ARRIVED IN CALLEE).*" \ "reverse step into fn call" -# step backward out of called function (thru call) +# step backward out of called function (through call) set test_message "reverse step out of called fn" gdb_test_multiple "step" "$test_message" { diff --git a/gdb/testsuite/gdb.reverse/step-reverse.exp b/gdb/testsuite/gdb.reverse/step-reverse.exp index 6f1e8b6..7bcb93b 100644 --- a/gdb/testsuite/gdb.reverse/step-reverse.exp +++ b/gdb/testsuite/gdb.reverse/step-reverse.exp @@ -108,7 +108,7 @@ gdb_test_multiple "stepi" "$test_message" { } } -# stepi thru return of a function call +# stepi through return of a function call set test_message "stepi back from function call" gdb_test_multiple "stepi" "$test_message" { @@ -140,7 +140,7 @@ gdb_test_multiple "stepi" "$test_message" { gdb_test_no_output "set exec-dir reverse" "set reverse execution" -# stepi backward thru return and into a function +# stepi backward through return and into a function set stepi_location [gdb_get_line_number "ARRIVED IN CALLEE" "$srcfile"] set test_message "reverse stepi thru function return" @@ -211,12 +211,12 @@ gdb_test_multiple "stepi" "$test_message" { } } -# step backward into function (thru return) +# step backward into function (through return) gdb_test "step" "(RETURN FROM CALLEE|ARRIVED IN CALLEE).*" \ "reverse step into fn call" -# step backward out of called function (thru call) +# step backward out of called function (through call) set test_message "reverse step out of called fn" gdb_test_multiple "step" "$test_message" { diff --git a/gdb/testsuite/gdb.threads/thread_check.exp b/gdb/testsuite/gdb.threads/thread_check.exp index 52c6fa4..7dd7ff4 100644 --- a/gdb/testsuite/gdb.threads/thread_check.exp +++ b/gdb/testsuite/gdb.threads/thread_check.exp @@ -48,7 +48,7 @@ if ![runto_main] then { # -# set breakpoint at thread fucntion tf +# set breakpoint at thread function tf # gdb_test "break tf" \ "Breakpoint.*at.* file .*$srcfile, line.*" \ diff --git a/gdb/testsuite/gdb.trace/collection.exp b/gdb/testsuite/gdb.trace/collection.exp index f225429..8107802 100644 --- a/gdb/testsuite/gdb.trace/collection.exp +++ b/gdb/testsuite/gdb.trace/collection.exp @@ -163,7 +163,7 @@ proc gdb_collect_args_test { myargs msg } { # collected. In C, an array as function parameters is a special # case; it's just a pointer into the caller's array, and as such, # that's what normally the debug info describes. Maybe this was - # originaly written for a compiler where array parameters were + # originally written for a compiler where array parameters were # really described as arrays in debug info. setup_xfail "*-*-*" @@ -249,7 +249,7 @@ proc gdb_collect_argarray_test { myargs msg } { # collected. In C, an array as function parameters is a special # case; it's just a pointer into the caller's array, and as such, # that's what normally the debug info describes. Maybe this was - # originaly written for a compiler where array parameters were + # originally written for a compiler where array parameters were # really described as arrays in debug info. setup_xfail "*-*-*" diff --git a/gdb/testsuite/gdb.trace/mi-tracepoint-changed.exp b/gdb/testsuite/gdb.trace/mi-tracepoint-changed.exp index a0e49af..ecde32c 100644 --- a/gdb/testsuite/gdb.trace/mi-tracepoint-changed.exp +++ b/gdb/testsuite/gdb.trace/mi-tracepoint-changed.exp @@ -157,7 +157,7 @@ proc test_reconnect { } { } } -# Test 'breakpoint-modified' notification is emited when pending tracepoints are +# Test 'breakpoint-modified' notification is emitted when pending tracepoints are # resolved. proc test_pending_resolved { } { diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp index e1e9880..bab99b3 100644 --- a/gdb/testsuite/lib/gdb.exp +++ b/gdb/testsuite/lib/gdb.exp @@ -1015,7 +1015,7 @@ proc gdb_test { args } { # Send a command to GDB and verify that this command generated no output. # # See gdb_test_multiple for a description of the COMMAND and MESSAGE -# parameters. If MESSAGE is ommitted, then COMMAND will be used as +# parameters. If MESSAGE is omitted, then COMMAND will be used as # the message. (If MESSAGE is the empty string, then sometimes we do not # call pass or fail at all; I don't understand this at all.) @@ -1249,7 +1249,7 @@ proc gdb_test_list_exact { cmd name elm_find_regexp elm_extract_regexp result_ma # # Both inferior and gdb patterns must match for a PASS. # -# If MESSAGE is ommitted, then COMMAND will be used as the message. +# If MESSAGE is omitted, then COMMAND will be used as the message. # # Returns: # 1 if the test failed, @@ -3512,7 +3512,7 @@ proc gdb_compile {source dest type options} { # Force output to unbuffered mode, by linking in an object file # with a global contructor that calls setvbuf. # - # Compile the special object seperatelly for two reasons: + # Compile the special object separately for two reasons: # 1) Insulate it from $options. # 2) Avoid compiling it for every gdb_compile invocation, # which is time consuming, especially if we're remote @@ -5553,7 +5553,7 @@ proc get_integer_valueof { exp default } { # Retrieve the value of EXP in the inferior, as an hexadecimal value # (using "print /x"). DEFAULT is used as fallback if print fails. -# TEST is the test message to use. If can be ommitted, in which case +# TEST is the test message to use. If can be omitted, in which case # a test message is built from EXP. proc get_hexadecimal_valueof { exp default {test ""} } { diff --git a/gdb/testsuite/lib/prelink-support.exp b/gdb/testsuite/lib/prelink-support.exp index 0584669..1b45278 100644 --- a/gdb/testsuite/lib/prelink-support.exp +++ b/gdb/testsuite/lib/prelink-support.exp @@ -70,7 +70,7 @@ proc symlink_resolve {file} { } # Copy SRC to DEST, resolving any symlinks in SRC. Return nonzero iff -# the copy was succesful. +# the copy was successful. # # This function is guaranteed to never raise any exception, even when the copy # fails. @@ -107,7 +107,7 @@ proc file_copy {src dest} { # depend on system libraries. To properly prelink an executable, all # of its dynamically linked libraries must be prelinked as well. If # the executable depends on some system libraries, we may not have -# sufficient write priviledges on these files to perform the prelink. +# sufficient write privileges on these files to perform the prelink. # This is why we make a copy of these shared libraries, and link the # executable against these copies instead. #