Corrected spelling errors in comments.

gdbarch.{c,sh} removed a word from a comment.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index c9773ce9562162436a074e8d6270f847c1421ed9..c889e1b3799fa26ad5f36046754b9d0561c3da4b 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,11 @@
+2000-10-26  David B. Anderson <davea@sgi.com>
+
+       * breakpoint.c breakpoint.h hppab-nat.c infrun.c
+       language.h mcore-tdep.c mips-tdep.c symfile.c symtab.c
+       symtab.h target.c tm-mips.h xm-sun4sol2.h: Corrected
+       spelling errors in comments.
+       * gdbarch.c gdbarch.sh: Removed word from comment.
+
 2000-10-26  Kevin Buettner  <kevinb@redhat.com>
 
        * sun3-nat.c (fetch_core_registers): Protoize.

diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index 489aad2ee9d3bb4790d56a146981486db98d0e3f..31c6c6ea6f5235fa56645c8e258754645aa6d3c5 100644 (file)
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -1266,7 +1266,7 @@ remove_breakpoint (struct breakpoint *b, insertion_state_t is)
          /* Check to see if breakpoint is in an overlay section;
             if so, we should remove the breakpoint at the LMA address.
             If that is not equal to the raw address, then we should 
-            presumable remove the breakpoint there as well.  */
+            presumably remove the breakpoint there as well.  */
          if (overlay_debugging && b->section &&
              section_is_overlay (b->section))
            {
@@ -2780,7 +2780,7 @@ bpstat_what (bpstat bs)
      back and decide something of a lower priority is better.  The
      ordering is:
 
-     kc   < clr sgl shl slr sn sr ss ts
+     kc   < clr sgl shl shlr slr sn sr ss ts
      sgl  < clrs shl shlr slr sn sr ss ts
      slr  < err shl shlr sn sr ss ts
      clr  < clrs err shl shlr sn sr ss ts

diff --git a/gdb/breakpoint.h b/gdb/breakpoint.h
index c25ab41f8faac1bfb8d1a1ee82a8e390b0c8de02..6fef5bd2e2bdfd3541912165ed1dd3670946a125 100644 (file)
--- a/gdb/breakpoint.h
+++ b/gdb/breakpoint.h
@@ -280,17 +280,17 @@ struct breakpoint
     char *dll_pathname;
 
     /* Filename of a dll whose state change (e.g., load or unload)
-       triggered this catchpoint.  This field is only vaid immediately
+       triggered this catchpoint.  This field is only valid immediately
        after this catchpoint has triggered.  */
     char *triggered_dll_pathname;
 
     /* Process id of a child process whose forking triggered this
-       catchpoint.  This field is only vaid immediately after this
+       catchpoint.  This field is only valid immediately after this
        catchpoint has triggered.  */
     int forked_inferior_pid;
 
     /* Filename of a program whose exec triggered this catchpoint.
-       This field is only vaid immediately after this catchpoint has
+       This field is only valid immediately after this catchpoint has
        triggered.  */
     char *exec_pathname;
 
@@ -620,7 +620,7 @@ extern void set_longjmp_resume_breakpoint (CORE_ADDR, struct frame_info *);
    cause the inferior to stop in places where this frame is visible,
    and that can cause execution control to become very confused.
 
-   Note that if a user sets breakpoints in an interactively call
+   Note that if a user sets breakpoints in an interactively called
    function, the call_disabled watchpoints will have been reenabled
    when the first such breakpoint is reached.  However, on targets
    that are unable to unwind through the call dummy frame, watches

diff --git a/gdb/config/mips/tm-mips.h b/gdb/config/mips/tm-mips.h
index 653b62d068ea4a9ed643bc03efa458fae9493230..f4dd60cc6c0d86f84d70a43263b55da9182b83c6 100644 (file)
--- a/gdb/config/mips/tm-mips.h
+++ b/gdb/config/mips/tm-mips.h
@@ -432,7 +432,7 @@ extern void mips_print_extra_frame_info (struct frame_info *frame);
    multiple functions with the same SP.  But on the MIPS we can't do
    that since the PC is not stored in the same part of the frame every
    time.  This does not seem to be a very clever way to set up frames,
-   but there is nothing we can do about that).  */
+   but there is nothing we can do about that.  */
 
 #define SETUP_ARBITRARY_FRAME(argc, argv) setup_arbitrary_frame (argc, argv)
 extern struct frame_info *setup_arbitrary_frame (int, CORE_ADDR *);

diff --git a/gdb/config/sparc/xm-sun4sol2.h b/gdb/config/sparc/xm-sun4sol2.h
index 3edb5abdf545a926403ba4387baba059cba5b959..43f6166d132970959fc640cbe50f85e60373a080 100644 (file)
--- a/gdb/config/sparc/xm-sun4sol2.h
+++ b/gdb/config/sparc/xm-sun4sol2.h
@@ -39,5 +39,5 @@
 
 /* On sol2.7, <curses.h> emits a bunch of 'macro redefined'
    warnings, which makes autoconf think curses.h doesn't
-   exist.  Compensate fot that here. */
+   exist.  Compensate for that here. */
 #define HAVE_CURSES_H 1

diff --git a/gdb/gdbarch.c b/gdb/gdbarch.c
index bd705f913902a336aadbba2d4f8d5c169ff975fb..5754aa477103911c3295985db0ac80e2dbc4b78b 100644 (file)
--- a/gdb/gdbarch.c
+++ b/gdb/gdbarch.c
@@ -117,7 +117,7 @@ struct gdbarch
      verify_gdbarch(): Confirm that the target updated the field
      correctly.
 
-     gdbarch_dump(): Add a fprintf_unfiltered call to so that the new
+     gdbarch_dump(): Add a fprintf_unfiltered call so that the new
      field is dumped out
 
      ``startup_gdbarch()'': Append an initial value to the static

diff --git a/gdb/gdbarch.sh b/gdb/gdbarch.sh
index 11a4a779e50e98a0909b2719c21d92841a84c39c..0d827f77080089667a54b9153efc251cfb8fbdb8 100755 (executable)
--- a/gdb/gdbarch.sh
+++ b/gdb/gdbarch.sh
@@ -1102,7 +1102,7 @@ cat <<EOF
      verify_gdbarch(): Confirm that the target updated the field
      correctly.
 
-     gdbarch_dump(): Add a fprintf_unfiltered call to so that the new
+     gdbarch_dump(): Add a fprintf_unfiltered call so that the new
      field is dumped out
 
      \`\`startup_gdbarch()'': Append an initial value to the static

diff --git a/gdb/hppab-nat.c b/gdb/hppab-nat.c
index 5659532152a437d140def4f89667c933c52e19de..17a4dc763a340f7be21a73908d66380ba2058a63 100644 (file)
--- a/gdb/hppab-nat.c
+++ b/gdb/hppab-nat.c
@@ -182,7 +182,7 @@ store_inferior_registers (int regno)
 
    This call may fail if the given addresses are not valid in the inferior
    process.  This most often happens when restarting a program which
-   as watchpoints inserted on heap or stack memory.  */
+   has watchpoints inserted on heap or stack memory.  */
 
 #define PT_PROT 21
 

diff --git a/gdb/infrun.c b/gdb/infrun.c
index a753e5fcab47a5979a9147cfcdfd076163ea9029..4ff0fad10a8eb808c05bd04111b672eff90c5466 100644 (file)
--- a/gdb/infrun.c
+++ b/gdb/infrun.c
@@ -1108,7 +1108,7 @@ start_remote (void)
 
   /* Always go on waiting for the target, regardless of the mode. */
   /* FIXME: cagney/1999-09-23: At present it isn't possible to
-     indicate th wait_for_inferior that a target should timeout if
+     indicate to wait_for_inferior that a target should timeout if
      nothing is returned (instead of just blocking).  Because of this,
      targets expecting an immediate response need to, internally, set
      things up so that the target_wait() is forced to eventually

diff --git a/gdb/language.h b/gdb/language.h
index ba007786de26b4d05e219c19192860e5257e1836..503e338f71cfd1b810c951dbc3d12b3c284413ee 100644 (file)
--- a/gdb/language.h
+++ b/gdb/language.h
@@ -30,7 +30,7 @@ struct expression;
 /* enum exp_opcode;     ANSI's `wisdom' didn't include forward enum decls. */
 
 /* This used to be included to configure GDB for one or more specific
-   languages.  Now it is shortcutted to configure for all of them.  FIXME.  */
+   languages.  Now it is left out to configure for all of them.  FIXME.  */
 /* #include "lang_def.h" */
 #define        _LANG_c
 #define        _LANG_m2
@@ -255,7 +255,7 @@ struct language_defn
    its own language and we should keep track of that regardless of the
    language when symbols are read.  If we want some manual setting for
    the language of symbol files (e.g. detecting when ".c" files are
-   C++), it should be a seprate setting from the current_language.  */
+   C++), it should be a separate setting from the current_language.  */
 
 extern const struct language_defn *current_language;
 

diff --git a/gdb/mcore-tdep.c b/gdb/mcore-tdep.c
index d129d5fc8a67beaa37192f45a5aaced561d9f6c7..c47a1b58fbd04693bf02fb344daa81f0c8a6b123 100644 (file)
--- a/gdb/mcore-tdep.c
+++ b/gdb/mcore-tdep.c
@@ -615,7 +615,7 @@ mcore_skip_prologue (CORE_ADDR pc)
   struct symtab_and_line sal;
 
   /* If we have line debugging information, then the end of the
-     prologue should the first assembly instruction of  the first
+     prologue should be the first assembly instruction of the first
      source line */
   if (find_pc_partial_function (pc, NULL, &func_addr, &func_end))
     {

diff --git a/gdb/mips-tdep.c b/gdb/mips-tdep.c
index 0ca1eaf57adc0650db6929a018c44a2f25c8045d..dc6ecf8a662ad8058746268a22873958d6984585 100644 (file)
--- a/gdb/mips-tdep.c
+++ b/gdb/mips-tdep.c
@@ -1132,8 +1132,8 @@ mips16_next_pc (CORE_ADDR pc)
   return pc;
 }                              /* mips16_next_pc */
 
-/* The mips_next_pc function supports single_tep when the remote target monitor or
-   stub is not developed enough to so a single_step.
+/* The mips_next_pc function supports single_step when the remote 
+   target monitor or stub is not developed enough to do a single_step.
    It works by decoding the current instruction and predicting where a branch
    will go. This isnt hard because all the data is available.
    The MIPS32 and MIPS16 variants are quite different

diff --git a/gdb/symfile.c b/gdb/symfile.c
index 02f040466fbeef8633099a3c6cf0c326d0e9e08e..05fd4fbacf1aaf237e5cc0aecc5af5ed7c4b769f 100644 (file)
--- a/gdb/symfile.c
+++ b/gdb/symfile.c
@@ -2143,7 +2143,7 @@ cashier_psymtab (struct partial_symtab *pst)
    it is not called for subsidiary files such as .h files.
 
    Return value is 1 if we blew away the environment, 0 if not.
-   FIXME.  The return valu appears to never be used.
+   FIXME.  The return value appears to never be used.
 
    FIXME.  I think this is not the best way to do this.  We should
    work on being gentler to the environment while still cleaning up

diff --git a/gdb/symtab.c b/gdb/symtab.c
index 56a179514bc2623847cce9941a2bad0ef12d5164..d61207268140ee2dc6bdbeb4d6e61d5fbb4af5c4 100644 (file)
--- a/gdb/symtab.c
+++ b/gdb/symtab.c
@@ -1569,7 +1569,7 @@ done:
 }
 #endif /* 0 */
 
-/* Find the source file and line number for a given PC value and section.
+/* Find the source file and line number for a given PC value and SECTION.
    Return a structure containing a symtab pointer, a line number,
    and a pc range for the entire source line.
    The value's .pc field is NOT the specified pc.

diff --git a/gdb/symtab.h b/gdb/symtab.h
index d76df87c2532a3f6c152c8755becf6ca369bee2b..1195856a57afd0f689dc9816480844daef7f912a 100644 (file)
--- a/gdb/symtab.h
+++ b/gdb/symtab.h
@@ -761,7 +761,7 @@ struct partial_symbol
 \f
 
 /* Source-file information.  This describes the relation between source files,
-   ine numbers and addresses in the program text.  */
+   line numbers and addresses in the program text.  */
 
 struct sourcevector
   {
@@ -1417,7 +1417,7 @@ extern struct partial_symbol *fixup_psymbol_section (struct partial_symbol
 /* Symbol searching */
 
 /* When using search_symbols, a list of the following structs is returned.
-   Callers must free the search list using free_symbol_search! */
+   Callers must free the search list using free_search_symbols! */
 struct symbol_search
   {
     /* The block in which the match was found. Could be, for example,

diff --git a/gdb/target.c b/gdb/target.c
index 256dc643354ae249e206aef6cde9bd5926e7323b..4f4f8b042f2230e61710e8d6bf997fd84d9db4ed 100644 (file)
--- a/gdb/target.c
+++ b/gdb/target.c
@@ -2076,7 +2076,7 @@ store_waitstatus (struct target_waitstatus *ourstatus, int hoststatus)
    signal.  The idea is to keep these circumstances limited so that
    users (and scripts) develop portable habits.  For comparison,
    POSIX.2 `kill' requires that 1,2,3,6,9,14, and 15 work (and using a
-   numeric signal at all is obscelescent.  We are slightly more
+   numeric signal at all is obsolescent.  We are slightly more
    lenient and allow 1-15 which should match host signal numbers on
    most systems.  Use of symbolic signal names is strongly encouraged.  */