From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [PATCH] Check return value of bfd_init
Date: Thu, 25 Oct 2018 15:03:00 -0000 [thread overview]
Message-ID: <20181025150340.28844-1-tom@tromey.com> (raw)
Alan recently added a way for BFD library users to check whether they
were in fact loading a compatible version of BFD:
https://sourceware.org/ml/binutils/2018-10/msg00198.html
It seemed reasonable to me that gdb should do this check as well, in
case someone is dynamically linking against BFD. Tested by rebuilding
and then starting the resulting gdb.
gdb/ChangeLog
2018-10-25 Tom Tromey <tom@tromey.com>
* main.c (captured_main_1): Check return value of bfd_init.
---
gdb/ChangeLog | 4 ++++
gdb/main.c | 3 ++-
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 61dc039d4fe..a90c2978185 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2018-10-25 Tom Tromey <tom@tromey.com>
+
+ * main.c (captured_main_1): Check return value of bfd_init.
+
2018-10-25 Andrew Burgess <andrew.burgess@embecosm.com>
* python/py-function.c (convert_values_to_python): Return
diff --git a/gdb/main.c b/gdb/main.c
index 8709357e924..96def3080eb 100644
--- a/gdb/main.c
+++ b/gdb/main.c
@@ -506,7 +506,8 @@ captured_main_1 (struct captured_main_args *context)
textdomain (PACKAGE);
#endif
- bfd_init ();
+ if (bfd_init () != BFD_INIT_MAGIC)
+ error (_("fatal error: libbfd ABI mismatch"));
notice_open_fds ();
saved_command_line = (char *) xstrdup ("");
--
2.17.2
next reply other threads:[~2018-10-25 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 15:03 Tom Tromey [this message]
2018-10-25 15:25 ` Simon Marchi
[not found] ` <87efcehwlx.fsf@tromey.com>
2018-10-26 15:41 ` Tom Tromey
2018-10-26 18:31 ` Simon Marchi
2018-10-26 19:48 ` Tom Tromey
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=20181025150340.28844-1-tom@tromey.com \
--to=tom@tromey.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