From: Tom Tromey <tromey@adacore.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH] Do not write negative PID or TID in remote protocol
Date: Thu, 30 Apr 2026 11:33:09 -0600 [thread overview]
Message-ID: <87o6j0ica2.fsf@tromey.com> (raw)
In-Reply-To: <20260312124203.14b9e893@f42-zbm-amd> (Kevin Buettner's message of "Thu, 12 Mar 2026 12:42:03 -0700")
>>>>> "Kevin" == Kevin Buettner <kevinb@redhat.com> writes:
>> This patch attempts to fix the bug. I am not really sure how to test
>> it.
>>
>> As an aside there seems to be more low-level RSP code that could be
>> shared here.
Kevin> LGTM.
Kevin> FWIW, Claude Opus 4.6 suggested that unit test might be employed for
Kevin> testing these changes. I'm not sure that's necessary, but I thought I'd
Kevin> mention it.
Yeah, good advice.
And doing this pointed out a problem. I'll send v2 shortly.
Tom
next prev parent reply other threads:[~2026-04-30 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 20:21 Tom Tromey
2026-03-12 19:42 ` Kevin Buettner
2026-04-30 17:33 ` Tom Tromey [this message]
2026-04-30 17:59 Tom Tromey
2026-06-12 15:23 ` Tom Tromey
2026-07-01 17:47 ` Tom Tromey
2026-07-02 10:18 ` Mark Wielaard
2026-07-02 18:29 ` Tom Tromey
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=87o6j0ica2.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@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