From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix "set debug parser"
Date: Mon, 28 Apr 2025 16:29:43 -0600 [thread overview]
Message-ID: <87r01bdinc.fsf@tromey.com> (raw)
In-Reply-To: <d23b7174-63bf-40cb-b55f-539a207eafac@suse.de> (Tom de Vries's message of "Mon, 28 Apr 2025 12:50:08 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> - the gdb_test_multiple doesn't consume the prompt, which causes
Tom> problems for subsequent tests (currently none)
I don't think I realized this.
gdb_test_multiple seems kind of hard to use TBH.
Tom> So, I get to this fixup patch:
I applied this, thanks.
I'm going to check this in since I was needing it to debug my other
series anyhow.
Tom
next prev parent reply other threads:[~2025-04-28 22:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-26 23:12 Tom Tromey
2025-04-28 10:50 ` Tom de Vries
2025-04-28 22:29 ` Tom Tromey [this message]
2025-04-29 7:42 ` Tom de Vries
2025-05-02 20:30 ` Simon Marchi
2025-05-03 14:26 ` Simon Marchi
2025-05-03 17:26 ` Tom Tromey
2025-05-03 17:25 ` 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=87r01bdinc.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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