From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCHv3 1/2] gdbserver: Add mechanism to prevent sending T stop packets
Date: Mon, 02 Mar 2020 12:24:00 -0000 [thread overview]
Message-ID: <d9913192-e32b-259b-4580-d6282a26d115@redhat.com> (raw)
In-Reply-To: <27befec6c761c43f2e1a9e59403644c198cbd75b.1583149853.git.andrew.burgess@embecosm.com>
On 3/2/20 11:54 AM, Andrew Burgess wrote:
> There is a developer only feature in gdbserver that provides a
> command line option --disable-packet that prevents some packets from
> being sent, which is used to increase test coverage within GDB.
>
> This commit extends this mechanism to prevent GDBserver from sending
> the T stop reply packets, instead limiting GDBserver to only send the
> S stop reply packets.
>
> The S stop reply packet is part of the older target control mechanism,
> which has design flaws that were worked around with the introduction
> of the newer target control mechanism, which uses the T stop reply
> packet.
>
> Limiting GDBserver to use S stop packets instead of T stop packets
> will, inevitably, mean that GDBserver doesn't function correctly in
> many cases involving multiple threads, however, I don't think this is
> too important, this is a developer only feature, intended to allow us
> to test GDB.
>
> A new test that makes use of this feature will be added in the next
> commit.
>
> gdbserver/ChangeLog:
>
> * remote-utils.cc (prepare_resume_reply): Add ability to convert T
> reply into an S reply.
> * server.cc (disable_packet_T): New global.
> (captured_main): Set new global when appropriate.
> * server.h (disable_packet_T): Declare.
OK.
Thanks,
Pedro Alves
prev parent reply other threads:[~2020-03-02 12:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 7:35 [PATCH] gdb/remote: Ask target for current thread if it doesn't tell us Andrew Burgess
2020-02-26 18:52 ` Andrew Burgess
2020-02-26 19:28 ` Pedro Alves
2020-02-27 16:17 ` [PATCHv2] gdb/remote: Restore support for 'S' stop reply packet Andrew Burgess
2020-02-27 19:46 ` Pedro Alves
2020-02-28 14:03 ` Andrew Burgess
2020-02-28 17:46 ` Pedro Alves
2020-03-02 11:54 ` [PATCHv3 2/2] " Andrew Burgess
2020-03-02 12:25 ` Pedro Alves
2020-03-02 15:19 ` Andrew Burgess
2020-03-02 19:07 ` Pedro Alves
2020-03-02 19:25 ` Andrew Burgess
2020-03-09 17:35 ` Tom Tromey
2020-03-10 19:05 ` Andrew Burgess
2020-03-11 16:23 ` Andrew Burgess
2020-03-11 18:02 ` Tom Tromey
2020-03-02 11:54 ` [PATCHv3 0/2] " Andrew Burgess
[not found] ` <27befec6c761c43f2e1a9e59403644c198cbd75b.1583149853.git.andrew.burgess@embecosm.com>
2020-03-02 12:24 ` 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=d9913192-e32b-259b-4580-d6282a26d115@redhat.com \
--to=palves@redhat.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@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