From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Subject: Re: [PUSHED 5/6] gdb: use libbacktrace to create a better backtrace for fatal signals
Date: Wed, 29 Sep 2021 09:21:58 +0100 [thread overview]
Message-ID: <20210929082158.GK1900093@embecosm.com> (raw)
In-Reply-To: <f1dd4e64-07b5-a067-e031-89d1f8da5569@palves.net>
* Pedro Alves <pedro@palves.net> [2021-09-28 19:55:11 +0100]:
> Hi Andrew,
>
> I read this now (for the first time, I completely missed v1!), and spotted a couple typos:
>
> On 2021-09-28 12:26 p.m., Andrew Burgess wrote:
>
> > + return function != nullptr && strcmp (function, "main") == 0;
> > +}
> > +
> > +/* Write a backtrace to GDB's stderr in an async safe manor. This is a
>
> typo: manor -> manner.
>
> > +/* 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
>
> likewise.
>
>
> Thanks for doing all this.
Thanks, I fixed these. I also found an additional instance of this
mistake which I fixed.
Below is what I pushed.
Thanks,
Andrew
---
commit 80656a8e4b32353025f7f4cb1279168f082fbf7b
Author: Andrew Burgess <andrew.burgess@embecosm.com>
Date: Wed Sep 29 09:16:52 2021 +0100
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 b5e0a0ed004..8f826bde6b4 100644
--- 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 433aa23614b..a406041ec64 100644
--- 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 cec3ab03ed6..69101bd4074 100644
--- 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; }
next prev parent reply other threads:[~2021-09-29 8:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 9:49 [PATCH 0/6] Display GDB backtrace for internal errors Andrew Burgess
2021-08-19 9:49 ` [PATCH 1/6] gdb: use bool instead of int in struct internal_problem Andrew Burgess
2021-08-19 18:33 ` Simon Marchi
2021-09-07 14:11 ` Andrew Burgess
2021-08-19 9:49 ` [PATCH 2/6] gdb: make use of std::string in utils.c Andrew Burgess
2021-08-19 18:41 ` Simon Marchi
2021-09-07 14:12 ` Andrew Burgess
2021-08-19 9:49 ` [PATCH 3/6] gdb: Add a dependency between gdb and libbacktrace Andrew Burgess
2021-08-19 18:43 ` Simon Marchi
2021-08-27 17:44 ` Tom Tromey
2021-08-30 20:33 ` Andrew Burgess
2021-08-19 9:49 ` [PATCH 4/6] Copy in libbacktrace from gcc Andrew Burgess
2021-08-27 17:46 ` Tom Tromey
2021-08-30 20:34 ` Andrew Burgess
2021-08-19 9:49 ` [PATCH 5/6] gdb: use libbacktrace to create a better backtrace for fatal signals Andrew Burgess
2021-08-19 18:58 ` Simon Marchi
2021-08-19 9:49 ` [PATCH 6/6] gdb: print backtrace for internal error/warning Andrew Burgess
2021-08-19 19:01 ` Simon Marchi
2021-08-30 14:16 ` [PATCH 0/6] Display GDB backtrace for internal errors Tom de Vries
2021-08-30 20:35 ` Andrew Burgess
2021-08-31 11:17 ` Florian Weimer
2021-09-28 11:26 ` [PUSHED " Andrew Burgess
2021-09-28 11:26 ` [PUSHED 1/6] top-level configure: setup target_configdirs based on repository Andrew Burgess
2021-09-28 11:26 ` [PUSHED 2/6] gdb: Add a dependency between gdb and libbacktrace Andrew Burgess
2021-09-28 11:26 ` [PUSHED 4/6] src-release.sh: add libbacktrace to GDB_SUPPORT_DIRS Andrew Burgess
2021-09-28 11:26 ` [PUSHED 5/6] gdb: use libbacktrace to create a better backtrace for fatal signals Andrew Burgess
2021-09-28 18:55 ` Pedro Alves
2021-09-29 8:21 ` Andrew Burgess [this message]
2021-09-29 3:09 ` Simon Marchi
2021-09-29 9:56 ` Andrew Burgess
2021-09-28 11:26 ` [PUSHED 6/6] gdb: print backtrace for internal error/warning Andrew Burgess
2021-09-28 12:26 ` Eli Zaretskii
2021-09-29 8:34 ` Andrew Burgess
2021-09-28 12:20 ` [PUSHED 3/6] Copy in libbacktrace from gcc Andrew Burgess
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210929082158.GK1900093@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).