public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Gary Benson <gbenson@redhat.com>
To: Simon Marchi <simark@simark.ca>
Cc: Simon Marchi <simon.marchi@ericsson.com>,
		"Metzger, Markus T" <markus.t.metzger@intel.com>,
	Pedro Alves <palves@redhat.com>,
		"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] infrun: step through indirect branch thunks
Date: Tue, 17 Apr 2018 13:32:00 -0000	[thread overview]
Message-ID: <CAHegJi+6vNTtr6YcF3pBGw7fbeu0whBmMZnD2wvJP5Eqo2K=LQ@mail.gmail.com> (raw)
In-Reply-To: <3b0a79d5-88f3-0ae8-0d8d-4faf5434580f@simark.ca>

On Sun, Apr 15, 2018 at 8:47 PM, Simon Marchi <simark@simark.ca> wrote:
> Ok, so actually this happened with _not_ using --enable-targets=all.  I just
> pushed a patch which should fix it:
>
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=eda4efb12763893b8a49c10c6f2823a465c1c6ba

Thanks Simon!

      parent reply	other threads:[~2018-04-17 13:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19  5:16 Markus Metzger
2018-03-26 17:38 ` Pedro Alves
2018-04-09 14:20   ` Metzger, Markus T
2018-04-09 14:42     ` [pushed/ob] Apply "Convert observers to C++" edit to gdbarch.sh (Re: [PATCH] infrun: step through indirect branch thunks) Pedro Alves
2018-04-09 15:04     ` [PATCH] infrun: step through indirect branch thunks Pedro Alves
2018-04-09 16:24       ` Metzger, Markus T
2018-04-09 16:29         ` Pedro Alves
2018-04-10  9:02       ` Metzger, Markus T
2018-04-10  9:10         ` Pedro Alves
2018-04-13 14:58         ` Gary Benson
2018-04-13 16:07           ` Simon Marchi
2018-04-15 19:47             ` Simon Marchi
2018-04-16  6:51               ` Metzger, Markus T
2018-04-17 13:32               ` Gary Benson [this message]

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='CAHegJi+6vNTtr6YcF3pBGw7fbeu0whBmMZnD2wvJP5Eqo2K=LQ@mail.gmail.com' \
    --to=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=markus.t.metzger@intel.com \
    --cc=palves@redhat.com \
    --cc=simark@simark.ca \
    --cc=simon.marchi@ericsson.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).