From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <palves@redhat.com>,
Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: don't rely on inferior_ptid in gdbsim_target::wait
Date: Mon, 20 Jan 2020 15:48:00 -0000 [thread overview]
Message-ID: <3689d3ab-2df1-847d-38f6-3654d421edf7@polymtl.ca> (raw)
In-Reply-To: <25d128db-0f20-b812-a4e9-dbdc183986a2@redhat.com>
On 2020-01-20 10:13 a.m., Pedro Alves wrote:
> Thanks for doing this. This was a recent assertion I added with
> the multi-target work. It's possibly (and likely) that other ports
> will need similar adjustments, but it's hard to tell with actually
> running into the issue.
For the record, this commit [1] helped me understand that this was expected, and
that not using inferior_ptid was indeed the right fix.
[1] https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=e7af6c702da7a77529afdeffbbe6e13639beb441
Simon
prev parent reply other threads:[~2020-01-20 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 16:07 Simon Marchi
2020-01-19 23:23 ` Andrew Burgess
2020-01-20 0:49 ` Simon Marchi
2020-01-20 15:28 ` Pedro Alves
2020-01-20 15:48 ` Simon Marchi [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=3689d3ab-2df1-847d-38f6-3654d421edf7@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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