[gdb] Fix more common misspellings

Fix the following common misspellings:
...
addres -> address, adders
behavour -> behavior, behaviour
intented -> intended, indented
ther -> there, their, the
throught -> thought, through, throughout
...

Tested on x86_64-linux.

gdb/amd64-windows-tdep.c

@@ -324,7 +324,7 @@ amd64_windows_push_dummy_call
   /* Pass "hidden" argument".  */
   if (return_method == return_method_struct)
     {
-      /* The "hidden" argument is passed throught the first argument
+      /* The "hidden" argument is passed through the first argument
 	 register.  */
       const int arg_regnum = amd64_windows_dummy_call_integer_regs[0];
 

gdb/i386-fbsd-nat.c

@@ -254,7 +254,7 @@ i386_fbsd_nat_target::resume (ptid_t ptid, int step, enum gdb_signal signal)
       request = PT_CONTINUE;
     }
 
-  /* An addres of (caddr_t) 1 tells ptrace to continue from where it
+  /* An address of (caddr_t) 1 tells ptrace to continue from where it
      was.  (If GDB wanted it to start some other way, we have already
      written a new PC value to the child.)  */
   if (ptrace (request, pid, (caddr_t) 1,

gdb/mdebugread.c

@@ -413,7 +413,7 @@ static struct parse_stack
 
     struct type *cur_type;	/* Type we parse fields for.  */
     int cur_field;		/* Field number in cur_type.  */
-    CORE_ADDR procadr;		/* Start addres of this procedure.  */
+    CORE_ADDR procadr;		/* Start address of this procedure.  */
     int numargs;		/* Its argument count.  */
   }
 

gdb/rs6000-aix-tdep.c

@@ -524,7 +524,7 @@ rs6000_push_dummy_call (struct gdbarch *gdbarch, struct value *function,
      on PPC variants that lack them.  */
   gdb_assert (ppc_floating_point_unit_p (gdbarch));
 
-  /* The first eight words of ther arguments are passed in registers.
+  /* The first eight words of the arguments are passed in registers.
      Copy them appropriately.  */
   ii = 0;
 

gdb/rs6000-lynx178-tdep.c

@@ -56,7 +56,7 @@ rs6000_lynx178_push_dummy_call (struct gdbarch *gdbarch,
      on PPC variants that lack them.  */
   gdb_assert (ppc_floating_point_unit_p (gdbarch));
 
-  /* The first eight words of ther arguments are passed in registers.
+  /* The first eight words of the arguments are passed in registers.
      Copy them appropriately.  */
   ii = 0;
 

gdb/stubs/ia64vms-stub.c

@@ -311,7 +311,7 @@ term_raw_write (const char *str, unsigned int len)
     LIB$SIGNAL (status);
 }
 
-/* Flush ther term buffer.  */
+/* Flush the term buffer.  */
 
 static void
 term_flush (void)

gdb/testsuite/gdb.ada/complete.exp

@@ -214,7 +214,7 @@ test_gdb_complete "ambiguous_f" \
 test_gdb_complete "ambiguous_func" \
                   "p ambiguous_func"
 
-# Perform a test intented to verify the behavior where the number
+# Perform a test intended to verify the behavior where the number
 # of possible completions is very large.  The goal is not to verify
 # precisely the list returned by the complete command (this depends
 # on too many parameters -- targets, compiler version, runtime, etc).

gdb/testsuite/gdb.base/remote.exp

@@ -167,7 +167,7 @@ set sizeof_random_data [get_sizeof "random_data" 48*1024]
 clean_restart $binfile
 
 #
-# Part THREE: Check the upload behavour
+# Part THREE: Check the upload behavior.
 #
 if {![runto_main]} {
     return

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+
     #

gdb/ui.c

@@ -106,7 +106,7 @@ ui::input_interactive_p () const
 
 
 /* When there is an event ready on the stdin file descriptor, instead
-   of calling readline directly throught the callback function, or
+   of calling readline directly through the callback function, or
    instead of calling gdb_readline_no_editing_callback, give gdb a
    chance to detect errors and do something.  */