This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

FYI: fix duplicate words


I'm checking this in.

I noticed a little script from Jim Meyering to detect duplicate words,
so I ran it over gdb and then I fixed the fallout.

Mostly these are just duplicates; but a few were typos, and a couple
were made clearer, I thought, by the addition of a comma.

Tom

ChangeLog:
2011-04-19  Tom Tromey  <tromey@redhat.com>

	* windows-tdep.c (windows_xfer_shared_library):
	* windows-nat.c (get_module_name, windows_make_so):
	* v850-tdep.c (v850_handle_pushm):
	* utils.c (null_cleanup, gdb_realpath):
	* ui-out.c (get_next_header):
	* tracepoint.c (clear_traceframe_info):
	* symtab.c (lookup_symtab):
	* serial.h (struct serial_ops):
	* mipsread.c (read_alphacoff_dynamic_symtab):
	* infcmd.c (print_return_value):
	* ia64-linux-tdep.c (ia64_linux_sigcontext_register_address):
	* f-exp.y (parse_number):
	* exceptions.c (catch_exceptions):
	* dummy-frame.c (dummy_frame_this_id):
	* defs.h (struct cleanup):
	* breakpoint.c (disable_breakpoints_in_unloaded_shlib):
	* arm-tdep.c (arm_push_dummy_call):
	* amd64-tdep.h (amd64_collect_xsave):
	* amd64-tdep.c (amd64_collect_xsave):
	* alpha-tdep.c (alpha_heuristic_frame_unwind_cache):
	* README (typing): Remove duplicate words.
	* cli/cli-decode.c (lookup_cmd_composition): Add comma.
	* infrun.c (siginfo_value_read): Fix typo.
	* solib-frv.c (frv_fdpic_find_global_pointer): Likewise.
	* top.c (source_line_number): Add comma.

doc/ChangeLog:
2011-04-19  Tom Tromey  <tromey@redhat.com>

	* gdbint.texinfo (Register Information Functions): Remove
	duplicate "the".
	* gdb.texinfo (Emacs): Remove duplicate "to".
	(GDB/MI Variable Objects): Remove duplicate "the".
	(General Query Packets): Likewise.

gdbserver/ChangeLog:
2011-04-19  Tom Tromey  <tromey@redhat.com>

	* win32-low.c (handle_load_dll): Remove duplicate "the".

testsuite/ChangeLog:
2011-04-19  Tom Tromey  <tromey@redhat.com>

	* gdb.mi/mi-nsmoribund.exp:
	* gdb.hp/gdb.objdbg/objdbg01.exp:
	* gdb.base/structs.exp (test_struct_returns):
	* gdb.base/call-sc.exp (test_scalar_returns):
	* gdb.base/bigcore.exp: Remove duplicate words.

Index: README
===================================================================
RCS file: /cvs/src/src/gdb/README,v
retrieving revision 1.47
diff -u -r1.47 README
--- README	7 Jun 2010 07:42:49 -0000	1.47
+++ README	19 Apr 2011 18:01:48 -0000
@@ -144,7 +144,7 @@
 `gdb-VERSION/texinfo' directory.
 
    If you have TeX and a DVI printer program installed, you can typeset
-and print this manual.  First switch to the the `gdb' subdirectory of
+and print this manual.  First switch to the `gdb' subdirectory of
 the main source directory (for example, to `gdb-VERSION/gdb') and then type:
 
       make doc/gdb.dvi
Index: alpha-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/alpha-tdep.c,v
retrieving revision 1.204
diff -u -r1.204 alpha-tdep.c
--- alpha-tdep.c	18 Mar 2011 18:52:29 -0000	1.204
+++ alpha-tdep.c	19 Apr 2011 18:01:48 -0000
@@ -1244,7 +1244,7 @@
 		 So we recognize only a few registers (t7, t9, ra) within
 		 the procedure prologue as valid return address registers.
 		 If we encounter a return instruction, we extract the
-		 the return address register from it.
+		 return address register from it.
 
 		 FIXME: Rewriting GDB to access the procedure descriptors,
 		 e.g. via the minimal symbol table, might obviate this
Index: amd64-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/amd64-tdep.c,v
retrieving revision 1.87
diff -u -r1.87 amd64-tdep.c
--- amd64-tdep.c	18 Mar 2011 18:52:29 -0000	1.87
+++ amd64-tdep.c	19 Apr 2011 18:01:48 -0000
@@ -2662,7 +2662,7 @@
     }
 }
 
-/* Similar to amd64_collect_fxsave, but but use XSAVE extended state.  */
+/* Similar to amd64_collect_fxsave, but use XSAVE extended state.  */
 
 void
 amd64_collect_xsave (const struct regcache *regcache, int regnum,
Index: amd64-tdep.h
===================================================================
RCS file: /cvs/src/src/gdb/amd64-tdep.h,v
retrieving revision 1.19
diff -u -r1.19 amd64-tdep.h
--- amd64-tdep.h	1 Jan 2011 15:32:57 -0000	1.19
+++ amd64-tdep.h	19 Apr 2011 18:01:48 -0000
@@ -101,7 +101,7 @@
 extern void amd64_collect_fxsave (const struct regcache *regcache, int regnum,
 				  void *fxsave);
 
-/* Similar to amd64_collect_fxsave, but but use XSAVE extended state.  */
+/* Similar to amd64_collect_fxsave, but use XSAVE extended state.  */
 extern void amd64_collect_xsave (const struct regcache *regcache,
 				 int regnum, void *xsave, int gcore);
 
Index: arm-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/arm-tdep.c,v
retrieving revision 1.343
diff -u -r1.343 arm-tdep.c
--- arm-tdep.c	7 Apr 2011 04:18:02 -0000	1.343
+++ arm-tdep.c	19 Apr 2011 18:01:49 -0000
@@ -3558,7 +3558,7 @@
 
   /* Walk through the list of args and determine how large a temporary
      stack is required.  Need to take care here as structs may be
-     passed on the stack, and we have to to push them.  */
+     passed on the stack, and we have to push them.  */
   nstack = 0;
 
   argreg = ARM_A1_REGNUM;
Index: breakpoint.c
===================================================================
RCS file: /cvs/src/src/gdb/breakpoint.c,v
retrieving revision 1.567
diff -u -r1.567 breakpoint.c
--- breakpoint.c	14 Apr 2011 02:20:21 -0000	1.567
+++ breakpoint.c	19 Apr 2011 18:01:50 -0000
@@ -6154,7 +6154,7 @@
   }
 }
 
-/* Disable any breakpoints that are in in an unloaded shared library.
+/* Disable any breakpoints that are in an unloaded shared library.
    Only apply to enabled breakpoints, disabled ones can just stay
    disabled.  */
 
Index: defs.h
===================================================================
RCS file: /cvs/src/src/gdb/defs.h,v
retrieving revision 1.289
diff -u -r1.289 defs.h
--- defs.h	4 Apr 2011 14:10:12 -0000	1.289
+++ defs.h	19 Apr 2011 18:01:50 -0000
@@ -258,7 +258,7 @@
    point in the chain.  Use discard_cleanups to remove cleanups
    from the chain back to a given point, not doing them.
 
-   If the argument is pointer to allocated memory, then you need to
+   If the argument is pointer to allocated memory, then you need
    to additionally set the 'free_arg' member to a function that will
    free that memory.  This function will be called both when the cleanup
    is executed and when it's discarded.  */
Index: dummy-frame.c
===================================================================
RCS file: /cvs/src/src/gdb/dummy-frame.c,v
retrieving revision 1.63
diff -u -r1.63 dummy-frame.c
--- dummy-frame.c	18 Mar 2011 18:52:30 -0000	1.63
+++ dummy-frame.c	19 Apr 2011 18:01:50 -0000
@@ -261,7 +261,7 @@
 /* Assuming that THIS_FRAME is a dummy, return its ID.  That ID is
    determined by examining the NEXT frame's unwound registers using
    the method dummy_id().  As a side effect, THIS dummy frame's
-   dummy cache is located and and saved in THIS_PROLOGUE_CACHE.  */
+   dummy cache is located and saved in THIS_PROLOGUE_CACHE.  */
 
 static void
 dummy_frame_this_id (struct frame_info *this_frame,
Index: exceptions.c
===================================================================
RCS file: /cvs/src/src/gdb/exceptions.c,v
retrieving revision 1.42
diff -u -r1.42 exceptions.c
--- exceptions.c	4 Apr 2011 18:13:04 -0000	1.42
+++ exceptions.c	19 Apr 2011 18:01:50 -0000
@@ -442,7 +442,7 @@
    be replaced by judicious use of QUIT.  */
 
 /* MAYBE: cagney/1999-11-05: catch_errors() in conjunction with
-   error() et al. could maintain a set of flags that indicate the the
+   error() et al. could maintain a set of flags that indicate the
    current state of each of the longjmp buffers.  This would give the
    longjmp code the chance to detect a longjmp botch (before it gets
    to longjmperror()).  Prior to 1999-11-05 this wasn't possible as
Index: f-exp.y
===================================================================
RCS file: /cvs/src/src/gdb/f-exp.y,v
retrieving revision 1.38
diff -u -r1.38 f-exp.y
--- f-exp.y	18 Mar 2011 13:51:41 -0000	1.38
+++ f-exp.y	19 Apr 2011 18:01:50 -0000
@@ -765,7 +765,7 @@
   
   /* If the number is too big to be an int, or it's got an l suffix
      then it's a long.  Work out if this has to be a long by
-     shifting right and and seeing if anything remains, and the
+     shifting right and seeing if anything remains, and the
      target int size is different to the target long size.
      
      In the expression below, we could have tested
Index: ia64-linux-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/ia64-linux-tdep.c,v
retrieving revision 1.24
diff -u -r1.24 ia64-linux-tdep.c
--- ia64-linux-tdep.c	9 Jan 2011 03:08:56 -0000	1.24
+++ ia64-linux-tdep.c	19 Apr 2011 18:01:50 -0000
@@ -47,7 +47,7 @@
 
 /* IA-64 GNU/Linux specific function which, given a frame address and
    a register number, returns the address at which that register may be
-   found.  0 is returned for registers which aren't stored in the the
+   found.  0 is returned for registers which aren't stored in the
    sigcontext structure.  */
 
 static CORE_ADDR
Index: infcmd.c
===================================================================
RCS file: /cvs/src/src/gdb/infcmd.c,v
retrieving revision 1.279
diff -u -r1.279 infcmd.c
--- infcmd.c	22 Mar 2011 14:39:40 -0000	1.279
+++ infcmd.c	19 Apr 2011 18:01:50 -0000
@@ -1394,7 +1394,7 @@
   /* FIXME: 2003-09-27: When returning from a nested inferior function
      call, it's possible (with no help from the architecture vector)
      to locate and return/print a "struct return" value.  This is just
-     a more complicated case of what is already being done in in the
+     a more complicated case of what is already being done in the
      inferior function call code.  In fact, when inferior function
      calls are made async, this will likely be made the norm.  */
 
Index: infrun.c
===================================================================
RCS file: /cvs/src/src/gdb/infrun.c,v
retrieving revision 1.472
diff -u -r1.472 infrun.c
--- infrun.c	7 Mar 2011 16:03:00 -0000	1.472
+++ infrun.c	19 Apr 2011 18:01:51 -0000
@@ -6196,7 +6196,7 @@
 
 /* The $_siginfo convenience variable is a bit special.  We don't know
    for sure the type of the value until we actually have a chance to
-   fetch the data.  The type can change depending on gdbarch, so it it
+   fetch the data.  The type can change depending on gdbarch, so it is
    also dependent on which thread you have selected.
 
      1. making $_siginfo be an internalvar that creates a new value on
Index: mipsread.c
===================================================================
RCS file: /cvs/src/src/gdb/mipsread.c,v
retrieving revision 1.37
diff -u -r1.37 mipsread.c
--- mipsread.c	7 Mar 2011 16:17:29 -0000	1.37
+++ mipsread.c	19 Apr 2011 18:01:51 -0000
@@ -240,7 +240,7 @@
 				 (file_ptr) 0, got_secsize))
     return;
 
-  /* Find the number of local GOT entries and the index for the the
+  /* Find the number of local GOT entries and the index for the
      first dynamic symbol in the GOT.  */
   for (dyninfo_p = dyninfo_secptr, dyninfo_end = dyninfo_p + dyninfo_secsize;
        dyninfo_p < dyninfo_end;
Index: serial.h
===================================================================
RCS file: /cvs/src/src/gdb/serial.h,v
retrieving revision 1.28
diff -u -r1.28 serial.h
--- serial.h	4 Mar 2011 19:23:42 -0000	1.28
+++ serial.h	19 Apr 2011 18:01:51 -0000
@@ -278,7 +278,7 @@
     int (*write_prim)(struct serial *scb, const void *buf, size_t count);
     /* Return that number of bytes that can be read from FD
        without blocking.  Return value of -1 means that the
-       the read will not block even if less that requested bytes
+       read will not block even if less that requested bytes
        are available.  */
     int (*avail)(struct serial *scb, int fd);
 
Index: solib-frv.c
===================================================================
RCS file: /cvs/src/src/gdb/solib-frv.c,v
retrieving revision 1.39
diff -u -r1.39 solib-frv.c
--- solib-frv.c	26 Feb 2011 02:07:08 -0000	1.39
+++ solib-frv.c	19 Apr 2011 18:01:51 -0000
@@ -1108,7 +1108,7 @@
       so = so->next;
     }
 
-  /* Didn't find it it any of the shared objects.  So assume it's in the
+  /* Didn't find it in any of the shared objects.  So assume it's in the
      main executable.  */
   return main_got ();
 }
Index: symtab.c
===================================================================
RCS file: /cvs/src/src/gdb/symtab.c,v
retrieving revision 1.265
diff -u -r1.265 symtab.c
--- symtab.c	9 Apr 2011 19:35:11 -0000	1.265
+++ symtab.c	19 Apr 2011 18:01:51 -0000
@@ -245,7 +245,7 @@
      PSYMTAB_TO_SYMTAB doesn't return a symtab, even though one has
      been created.  So, we need to run through the symtabs again in
      order to find the file.
-     XXX - This is a crock, and should be fixed inside of the the
+     XXX - This is a crock, and should be fixed inside of the
      symbol parsing routines.  */
   goto got_symtab;
 }
Index: top.c
===================================================================
RCS file: /cvs/src/src/gdb/top.c,v
retrieving revision 1.195
diff -u -r1.195 top.c
--- top.c	12 Mar 2011 22:59:24 -0000	1.195
+++ top.c	19 Apr 2011 18:01:52 -0000
@@ -294,7 +294,7 @@
 }
 #endif /* defined SIGHUP */
 
-/* Line number we are currently in in a file which is being sourced.  */
+/* Line number we are currently in, in a file which is being sourced.  */
 /* NOTE 1999-04-29: This variable will be static again, once we modify
    gdb to use the event loop as the default command loop and we merge
    event-top.c into this file, top.c.  */
Index: tracepoint.c
===================================================================
RCS file: /cvs/src/src/gdb/tracepoint.c,v
retrieving revision 1.221
diff -u -r1.221 tracepoint.c
--- tracepoint.c	4 Apr 2011 17:41:07 -0000	1.221
+++ tracepoint.c	19 Apr 2011 18:01:52 -0000
@@ -234,7 +234,7 @@
     }
 }
 
-/* Free and and clear the traceframe info cache of the current
+/* Free and clear the traceframe info cache of the current
    traceframe.  */
 
 static void
Index: ui-out.c
===================================================================
RCS file: /cvs/src/src/gdb/ui-out.c,v
retrieving revision 1.54
diff -u -r1.54 ui-out.c
--- ui-out.c	31 Mar 2011 14:32:48 -0000	1.54
+++ ui-out.c	19 Apr 2011 18:01:52 -0000
@@ -1048,7 +1048,7 @@
   uiout->table.header_next = uiout->table.header_last;
 }
 
-/* Extract the format information for the NEXT header and and advance
+/* Extract the format information for the NEXT header and advance
    the header pointer.  Return 0 if there was no next header.  */
 
 static int
Index: utils.c
===================================================================
RCS file: /cvs/src/src/gdb/utils.c,v
retrieving revision 1.251
diff -u -r1.251 utils.c
--- utils.c	1 Apr 2011 17:20:42 -0000	1.251
+++ utils.c	19 Apr 2011 18:01:52 -0000
@@ -581,7 +581,7 @@
 }
 
 /* Provide a known function that does nothing, to use as a base for
-   for a possibly long chain of cleanups.  This is useful where we
+   a possibly long chain of cleanups.  This is useful where we
    use the cleanup chain for handling normal cleanups as well as dealing
    with cleanups that need to be done as a result of a call to error().
    In such cases, we may not be certain where the first cleanup is, unless
@@ -3605,7 +3605,7 @@
   /* FIXME: cagney/2002-11-13:
 
      Method 2a: Use realpath() with a NULL buffer.  Some systems, due
-     to the problems described in in method 3, have modified their
+     to the problems described in method 3, have modified their
      realpath() implementation so that it will allocate a buffer when
      NULL is passed in.  Before this can be used, though, some sort of
      configure time test would need to be added.  Otherwize the code
Index: v850-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/v850-tdep.c,v
retrieving revision 1.117
diff -u -r1.117 v850-tdep.c
--- v850-tdep.c	18 Mar 2011 18:52:32 -0000	1.117
+++ v850-tdep.c	19 Apr 2011 18:01:53 -0000
@@ -401,7 +401,7 @@
   else
     reg_table = pushmh_reg_table;
 
-  /* Calculate the total size of the saved registers, and add it it to the
+  /* Calculate the total size of the saved registers, and add it to the
      immediate value used to adjust SP.  */
   for (i = 0; reg_table[i].mask != 0; i++)
     if (list12 & reg_table[i].mask)
Index: windows-nat.c
===================================================================
RCS file: /cvs/src/src/gdb/windows-nat.c,v
retrieving revision 1.216
diff -u -r1.216 windows-nat.c
--- windows-nat.c	7 Apr 2011 22:24:17 -0000	1.216
+++ windows-nat.c	19 Apr 2011 18:01:53 -0000
@@ -500,7 +500,7 @@
     do_windows_store_inferior_registers (regcache, r);
 }
 
-/* Get the name of a given module at at given base address.  If base_address
+/* Get the name of a given module at given base address.  If base_address
    is zero return the first loaded module (which is always the name of the
    executable).  */
 static int
@@ -743,7 +743,7 @@
 	  return so;
 	}
 
-      /* The symbols in a dll are offset by 0x1000, which is the the
+      /* The symbols in a dll are offset by 0x1000, which is the
 	 offset from 0 of the first byte in an image - because of the
 	 file header and the section alignment.  */
       cygwin_load_start = (CORE_ADDR) (uintptr_t) ((char *)
Index: windows-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/windows-tdep.c,v
retrieving revision 1.10
diff -u -r1.10 windows-tdep.c
--- windows-tdep.c	12 Jan 2011 01:23:29 -0000	1.10
+++ windows-tdep.c	19 Apr 2011 18:01:53 -0000
@@ -391,7 +391,7 @@
   obstack_grow_str (obstack, p);
   xfree (p);
   obstack_grow_str (obstack, "\"><segment address=\"");
-  /* The symbols in a dll are offset by 0x1000, which is the the
+  /* The symbols in a dll are offset by 0x1000, which is the
      offset from 0 of the first byte in an image - because of the file
      header and the section alignment.  */
   obstack_grow_str (obstack, paddress (gdbarch, load_addr + 0x1000));
Index: cli/cli-decode.c
===================================================================
RCS file: /cvs/src/src/gdb/cli/cli-decode.c,v
retrieving revision 1.93
diff -u -r1.93 cli-decode.c
--- cli/cli-decode.c	12 Mar 2011 22:59:24 -0000	1.93
+++ cli/cli-decode.c	19 Apr 2011 18:01:53 -0000
@@ -1528,7 +1528,7 @@
   
   while (1)
     { 
-      /* Go through as many command lists as we need to 
+      /* Go through as many command lists as we need to,
 	 to find the command TEXT refers to.  */
       
       prev_cmd = *cmd;
Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.819
diff -u -r1.819 gdb.texinfo
--- doc/gdb.texinfo	2 Apr 2011 04:31:43 -0000	1.819
+++ doc/gdb.texinfo	19 Apr 2011 18:01:58 -0000
@@ -24277,7 +24277,7 @@
 If you specify an absolute file name when prompted for the @kbd{M-x
 gdb} argument, then Emacs sets your current working directory to where
 your program resides.  If you only specify the file name, then Emacs
-sets your current working directory to to the directory associated
+sets your current working directory to the directory associated
 with the previous buffer.  In this case, @value{GDBN} may find your
 program by searching your environment's @code{PATH} variable, but on
 some operating systems it might not find the source.  So, although the
@@ -27276,7 +27276,7 @@
 @end smallexample
 
 If a fixed variable object for the @code{state} variable is created in
-this function, and we enter the recursive call, the the variable
+this function, and we enter the recursive call, the variable
 object will report the value of @code{state} in the top-level
 @code{do_work} invocation.  On the other hand, a floating variable
 object will report the value of @code{state} in the current frame.
@@ -33073,7 +33073,7 @@
 information associated with the variable.)
 
 @var{lm} is the (big endian, hex encoded) OS/ABI-specific encoding of the
-the load module associated with the thread local storage.  For example,
+load module associated with the thread local storage.  For example,
 a @sc{gnu}/Linux system will pass the link map address of the shared
 object associated with the thread local storage under consideration. 
 Other operating environments may choose to represent the load module
Index: doc/gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.329
diff -u -r1.329 gdbint.texinfo
--- doc/gdbint.texinfo	4 Feb 2011 19:10:12 -0000	1.329
+++ doc/gdbint.texinfo	19 Apr 2011 18:01:59 -0000
@@ -3607,7 +3607,7 @@
 for fuller control over how the registers are displayed.
 
 The access should be for the specified architecture, @var{gdbarch},
-with output to the the file specified by the User Interface
+with output to the file specified by the User Interface
 Independent Output file handle, @var{file} (@pxref{UI-Independent
 Output, , UI-Independent Output---the @code{ui_out}
 Functions}).
Index: gdbserver/win32-low.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbserver/win32-low.c,v
retrieving revision 1.53
diff -u -r1.53 win32-low.c
--- gdbserver/win32-low.c	7 Apr 2011 23:59:59 -0000	1.53
+++ gdbserver/win32-low.c	19 Apr 2011 18:02:00 -0000
@@ -1204,7 +1204,7 @@
     return;
 
   /* The symbols in a dll are offset by 0x1000, which is the
-     the offset from 0 of the first byte in an image - because
+     offset from 0 of the first byte in an image - because
      of the file header and the section alignment. */
 
   load_addr = (CORE_ADDR) (uintptr_t) event->lpBaseOfDll + 0x1000;
Index: testsuite/gdb.base/bigcore.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/bigcore.exp,v
retrieving revision 1.24
diff -u -r1.24 bigcore.exp
--- testsuite/gdb.base/bigcore.exp	1 Jan 2011 15:33:40 -0000	1.24
+++ testsuite/gdb.base/bigcore.exp	19 Apr 2011 18:02:02 -0000
@@ -32,7 +32,7 @@
 
 # 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 and
+# consumes too many resources - gigabytes worth of disk space and
 # I/O bandwith.
 
 if { [istarget "*-*-*bsd*"]
Index: testsuite/gdb.base/call-sc.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/call-sc.exp,v
retrieving revision 1.17
diff -u -r1.17 call-sc.exp
--- testsuite/gdb.base/call-sc.exp	1 Jan 2011 15:33:40 -0000	1.17
+++ testsuite/gdb.base/call-sc.exp	19 Apr 2011 18:02:02 -0000
@@ -189,7 +189,7 @@
 
     # The relevant code looks like "L{n} = fun{n}()".  The test forces
     # "fun{n}" to "return" with an explicit value.  Since that code
-    # snippet will store the the returned value in "L{n}" the return
+    # snippet will store the returned value in "L{n}" the return
     # is tested by examining "L{n}".  This assumes that the
     # compiler implemented this as fun{n}(&L{n}) and hence that when
     # the value isn't stored "L{n}" remains unchanged.  Also check for
Index: testsuite/gdb.base/structs.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/structs.exp,v
retrieving revision 1.34
diff -u -r1.34 structs.exp
--- testsuite/gdb.base/structs.exp	1 Jan 2011 15:33:43 -0000	1.34
+++ testsuite/gdb.base/structs.exp	19 Apr 2011 18:02:02 -0000
@@ -300,7 +300,7 @@
 
     # The relevant code looks like "L{n} = fun{n}()".  The test forces
     # "fun{n}" to "return" with an explicit value.  Since that code
-    # snippet will store the the returned value in "L{n}" the return
+    # snippet will store the returned value in "L{n}" the return
     # is tested by examining "L{n}".  This assumes that the
     # compiler implemented this as fun{n}(&L{n}) and hence that when
     # the value isn't stored "L{n}" remains unchanged.  Also check for
Index: testsuite/gdb.hp/gdb.objdbg/objdbg01.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.hp/gdb.objdbg/objdbg01.exp,v
retrieving revision 1.5
diff -u -r1.5 objdbg01.exp
--- testsuite/gdb.hp/gdb.objdbg/objdbg01.exp	7 Mar 2011 16:03:03 -0000	1.5
+++ testsuite/gdb.hp/gdb.objdbg/objdbg01.exp	19 Apr 2011 18:02:02 -0000
@@ -62,7 +62,7 @@
 for {set filenum 0} {$filenum < 2} {incr filenum 1} {
 
     # Lets test some commons
-    # Need to restart each to to make sure objects are not loaded
+    # Need to restart each to make sure objects are not loaded
     # Also cross check the address with what is actually in the
     #   object file (call the executable ${symaddrfile} to retrieve the
     #   information).
Index: testsuite/gdb.mi/mi-nsmoribund.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.mi/mi-nsmoribund.exp,v
retrieving revision 1.9
diff -u -r1.9 mi-nsmoribund.exp
--- testsuite/gdb.mi/mi-nsmoribund.exp	1 Jan 2011 15:33:47 -0000	1.9
+++ testsuite/gdb.mi/mi-nsmoribund.exp	19 Apr 2011 18:02:02 -0000
@@ -55,7 +55,7 @@
     continue
 }
 
-# Keep this in sync with THREADS in the the $srcfile.
+# Keep this in sync with THREADS in the $srcfile.
 set nthreads 10
 
 # Set a breakpoint and let all threads hit it (except the main


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]