From: Pedro Alves <palves@redhat.com>
To: Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdb/remote: do not check for null_ptid in stop reply (was: [PATCH] gdb: do not require ptid in stop reply if target does not support multi-process)
Date: Wed, 1 Apr 2020 15:43:17 +0100 [thread overview]
Message-ID: <f08687de-4f07-3d00-73de-c80c184bbdc3@redhat.com> (raw)
In-Reply-To: <20200401131726.13537-1-tankut.baris.aktemur@intel.com>
On 4/1/20 2:17 PM, Tankut Baris Aktemur wrote:
> gdb/ChangeLog:
> 2020-03-31 Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
>
> * remote.c (remote_target::remote_parse_stop_reply): Remove the
> check for no ptid in the stop reply when the target is non-stop.
>
> gdb/testsuite/ChangeLog:
> 2020-03-31 Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
>
> * gdb.server/stop-reply-no-thread.exp: Enhance the test
> scenario to cover execution until the end and also the case
> when no packet is disabled when starting gdbserver.
Perfect, thanks.
Pedro Alves
prev parent reply other threads:[~2020-04-01 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 13:17 Tankut Baris Aktemur
2020-04-01 14:43 ` Pedro Alves [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=f08687de-4f07-3d00-73de-c80c184bbdc3@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tankut.baris.aktemur@intel.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