Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Stephan Rohr <stephan.rohr@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] gdb, remote: Skip sending of 'vCont' package if remote target is empty
Date: Thu, 03 Sep 2026 11:43:41 -0600	[thread overview]
Message-ID: <874ig62pte.fsf@tromey.com> (raw)
In-Reply-To: <20260805085919.218925-3-stephan.rohr@intel.com> (Stephan Rohr's message of "Wed, 5 Aug 2026 08:59:18 +0000")

>>>>> Stephan Rohr <stephan.rohr@intel.com> writes:

> From: "Rohr, Stephan" <stephan.rohr@intel.com>
> If the remote target has no threads that need to be stopped, we can
> skip sending the 'vCont' package in 'remote_stop_ns'.

s/package/packet/

> +  /* Skip 'vCont' package if there are no threads to be stopped.  */

Here too.

> +# Test that we do not see a 'vCont' package if we interrupt an empty
> +# remote target.
> +gdb_test_multiple "interrupt -a" "no vCont is sent" {
> +    -re -wrap "vCont.*" {
> +	fail $gdb_test_name
> +    }
> +    -re -wrap "" {
> +	pass $gdb_test_name
> +    }

I'm a little concerned that this could hit the "overflow" issue if
there's a lot of output.  However often I feel we just ignore this
problem unless it crops up in practice.

> +  bool empty ()
> +  { return begin () == end (); }

Probably should be a const method.

Tom

  reply	other threads:[~2026-09-03 17:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05  8:59 [PATCH 0/2] gdb: improve interrupting an empty remote target Stephan Rohr
2026-08-05  8:59 ` [PATCH 1/2] gdb: fix assertion when " Stephan Rohr
2026-09-03 17:39   ` Tom Tromey
2026-08-05  8:59 ` [PATCH 2/2] gdb, remote: Skip sending of 'vCont' package if remote target is empty Stephan Rohr
2026-09-03 17:43   ` Tom Tromey [this message]
2026-08-17 14:37 ` [PATCH 0/2] gdb: improve interrupting an empty remote target Rohr, Stephan
2026-09-02 20:12   ` [Ping] " Rohr, Stephan

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=874ig62pte.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=stephan.rohr@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