diff options
author | Tom de Vries <tdevries@suse.de> | 2024-10-06 07:59:48 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2024-10-06 07:59:48 +0200 |
commit | 8f6606b6e3b568f6bbd3e2f0936eefb489e82a15 (patch) | |
tree | 17cbe5f6ae7a58b9ae24ab6c2727ca68477ef2b2 /gdb/target.c | |
parent | 67eca1ccc1ad5237403dc151eb91f5e506dea0c4 (diff) | |
download | binutils-8f6606b6e3b568f6bbd3e2f0936eefb489e82a15.zip binutils-8f6606b6e3b568f6bbd3e2f0936eefb489e82a15.tar.gz binutils-8f6606b6e3b568f6bbd3e2f0936eefb489e82a15.tar.bz2 |
[gdb] Fix common misspellings
Fix the following common misspellings:
...
accidently -> accidentally
additonal -> additional
addresing -> addressing
adress -> address
agaisnt -> against
albiet -> albeit
arbitary -> arbitrary
artifical -> artificial
auxillary -> auxiliary
auxilliary -> auxiliary
bcak -> back
begining -> beginning
cannonical -> canonical
compatiblity -> compatibility
completetion -> completion
diferent -> different
emited -> emitted
emiting -> emitting
emmitted -> emitted
everytime -> every time
excercise -> exercise
existance -> existence
fucntion -> function
funtion -> function
guarentee -> guarantee
htis -> this
immediatly -> immediately
layed -> laid
noone -> no one
occurances -> occurrences
occured -> occurred
originaly -> originally
preceeded -> preceded
preceeds -> precedes
propogate -> propagate
publically -> publicly
refering -> referring
substract -> subtract
substracting -> subtracting
substraction -> subtraction
taht -> that
targetting -> targeting
teh -> the
thier -> their
thru -> through
transfered -> transferred
transfering -> transferring
upto -> up to
vincinity -> vicinity
whcih -> which
whereever -> wherever
wierd -> weird
withing -> within
writen -> written
wtih -> with
doesnt -> doesn't
...
Tested on x86_64-linux.
Diffstat (limited to 'gdb/target.c')
-rw-r--r-- | gdb/target.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/target.c b/gdb/target.c index 962996f..4378c05 100644 --- a/gdb/target.c +++ b/gdb/target.c @@ -1754,7 +1754,7 @@ target_xfer_partial (struct target_ops *ops, If an error occurs, no guarantee is made about the contents of the data at MYADDR. In particular, the caller should not depend upon partial reads filling the buffer with good data. There is no way for the caller to know - how much good data might have been transfered anyway. Callers that can + how much good data might have been transferred anyway. Callers that can deal with partial reads should call target_read (which will retry until it makes no progress, and then return how much was transferred). */ |