From: Nick Clifton <nickc@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] Bug 29580 - typo in warning message: .note.gnu.build-id data size is too bug
Date: Tue, 20 Sep 2022 10:19:27 +0000 (GMT) [thread overview]
Message-ID: <20220920101927.5F0283858D38@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6af418600c451337814fe464eceea20c23ad231c
commit 6af418600c451337814fe464eceea20c23ad231c
Author: Zeke Lu <lvzecai@gmail.com>
Date: Tue Sep 20 11:19:06 2022 +0100
Bug 29580 - typo in warning message: .note.gnu.build-id data size is too bug
Diff:
---
binutils/dwarf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/binutils/dwarf.c b/binutils/dwarf.c
index f90f4efac5b..aef0f77eab6 100644
--- a/binutils/dwarf.c
+++ b/binutils/dwarf.c
@@ -11719,7 +11719,7 @@ load_build_id_debug_file (const char * main_filename ATTRIBUTE_UNUSED, void * ma
if (build_id_size > (section->size - 16))
{
- warn (_(".note.gnu.build-id data size is too bug\n"));
+ warn (_(".note.gnu.build-id data size is too big\n"));
return;
}
reply other threads:[~2022-09-20 10:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220920101927.5F0283858D38@sourceware.org \
--to=nickc@sourceware.org \
--cc=bfd-cvs@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).