Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tom@tromey.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Check return value of bfd_init
Date: Fri, 26 Oct 2018 18:31:00 -0000	[thread overview]
Message-ID: <4f3a2fce7baa5ee639c8ae514db50552@polymtl.ca> (raw)
In-Reply-To: <875zxoiulq.fsf@tromey.com>

On 2018-10-26 11:41, Tom Tromey wrote:
>>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
> 
> Tom> Moving the call to bfd_init below the call to "new ui" makes it 
> work.
> 
> Like so.
> 
> Tom
> 
> commit 2d0b2f3697a1f289e843f047697f252bf653d4db
> Author: Tom Tromey <tom@tromey.com>
> Date:   Thu Oct 25 09:00:52 2018 -0600
> 
>     Check return value of bfd_init
> 
>     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.
> 
>     Simon pointed out that an earlier version of the patch would cause 
> a
>     gdb crash if the test failed.  This version works around this by
>     lowering the call to bfd_init and adding a comment explaining where
>     'error' can safely be called in captured_main_1.
> 
>     gdb/ChangeLog
>     2018-10-25  Tom Tromey  <tom@tromey.com>
> 
>             * main.c (captured_main_1): Check return value of bfd_init.
> 
> 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..bf6a58180a0 100644
> --- a/gdb/main.c
> +++ b/gdb/main.c
> @@ -506,7 +506,6 @@ captured_main_1 (struct captured_main_args 
> *context)
>    textdomain (PACKAGE);
>  #endif
> 
> -  bfd_init ();
>    notice_open_fds ();
> 
>    saved_command_line = (char *) xstrdup ("");
> @@ -517,12 +516,17 @@ captured_main_1 (struct captured_main_args 
> *context)
>    setvbuf (stderr, NULL, _IONBF, BUFSIZ);
>  #endif
> 
> +  /* Note: `error' cannot be called before this point, because the
> +     caller will crash when trying to print the exception.  */
>    main_ui = new ui (stdin, stdout, stderr);
>    current_ui = main_ui;
> 
>    gdb_stdtargerr = gdb_stderr;	/* for moment */
>    gdb_stdtargin = gdb_stdin;	/* for moment */
> 
> +  if (bfd_init () == BFD_INIT_MAGIC)
> +    error (_("fatal error: libbfd ABI mismatch"));

The comparison operator is the wrong one (== instead of !=), you 
probably left it like this after testing.  LGTM with that fixed.

Simon


  reply	other threads:[~2018-10-26 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-25 15:03 Tom Tromey
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 [this message]
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=4f3a2fce7baa5ee639c8ae514db50552@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.com \
    --cc=tom@tromey.com \
    /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