From: William Tambe <tambewilliam@gmail.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb@sourceware.org
Subject: Re: sim_engine_halt() broken in binutils 2.34
Date: Tue, 04 Feb 2020 10:41:00 -0000 [thread overview]
Message-ID: <CAF8i9mNjF_BCEhcC8TdhD7pTM6sQ71W_8HRHPVNN37N0O08-1A@mail.gmail.com> (raw)
In-Reply-To: <20200204103251.GC20838@embecosm.com>
On Tue, Feb 4, 2020 at 5:32 AM Andrew Burgess
<andrew.burgess@embecosm.com> wrote:
>
> * William Tambe <tambewilliam@gmail.com> [2020-02-03 21:59:39 -0500]:
> >
> > I am using commit d7f734bc7e9e5fb6c33b433973b57e1eed3a7e9f (tag: binutils-2_34)
>
> You need to include:
>
> commit cf1d9e092f871df3b34a58cfcde915c689ac9067
> Date: Sun Jan 19 19:47:49 2020 -0500
>
> sim: don't rely on inferior_ptid in gdbsim_target::wait
Thank you very much; it fixed the issue after cherry-picking the above commit.
>
>
> Thanks,
> Andrew
prev parent reply other threads:[~2020-02-04 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 5:03 William Tambe
2020-02-02 21:47 ` Andrew Burgess
2020-02-03 2:12 ` William Tambe
2020-02-03 10:05 ` Andrew Burgess
2020-02-04 2:59 ` William Tambe
2020-02-04 10:32 ` Andrew Burgess
2020-02-04 10:41 ` William Tambe [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=CAF8i9mNjF_BCEhcC8TdhD7pTM6sQ71W_8HRHPVNN37N0O08-1A@mail.gmail.com \
--to=tambewilliam@gmail.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb@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