gdb: fix manor -> manner typo in some comments

In a recent commit I used 'manor' in some comments rather than
'manner'.  This commit fixes those two mistakes.

I also looked through the gdb/ tree and found one additional instance
of this mistake that this commit also fixes.

diff --git a/gdb/bt-utils.c b/gdb/bt-utils.c
index b5e0a0ed004bd3177ab691414201d80428d012b1..8f826bde6b4b57d822db9227a4893e6981a64862 100644 (file)
--- a/gdb/bt-utils.c
+++ b/gdb/bt-utils.c
@@ -108,7 +108,7 @@ libbacktrace_print (void *data, uintptr_t pc, const char *filename,
   return function != nullptr && strcmp (function, "main") == 0;
 }
 
-/* Write a backtrace to GDB's stderr in an async safe manor.  This is a
+/* Write a backtrace to GDB's stderr in an async safe manner.  This is a
    backtrace of GDB, not any running inferior, and is to be used when GDB
    crashes or hits some other error condition.  */
 

diff --git a/gdb/bt-utils.h b/gdb/bt-utils.h
index 433aa23614b3c8e218382ec920430e7ebbdbdf34..a406041ec64f47e9cec520f48c76c4f9075adf75 100644 (file)
--- a/gdb/bt-utils.h
+++ b/gdb/bt-utils.h
@@ -49,7 +49,7 @@
 #endif
 
 /* Print a backtrace of the current GDB process to the current
-   gdb_stderr.  The output is done in a signal async manor, so it is safe
+   gdb_stderr.  The output is done in a signal async manner, so it is safe
    to call from signal handlers.  */
 
 extern void gdb_internal_backtrace ();

diff --git a/gdb/language.h b/gdb/language.h
index cec3ab03ed65f1b855fa9311516b580bfe9ad0a1..69101bd4074adee87fc59382072db32969a5eb31 100644 (file)
--- a/gdb/language.h
+++ b/gdb/language.h
@@ -574,7 +574,7 @@ struct language_defn
   /* Return false if the language has first-class arrays.  Return true if
      there are no array values, and array objects decay to pointers, as in
      C.  The default is true as currently most supported languages behave
-     in this manor.  */
+     in this manner.  */
 
   virtual bool c_style_arrays_p () const
   { return true; }