From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@efficios.com>,
Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH] gdb/testsuite: fix gdb.gdb/selftest.exp for native-extended-gdbserver
Date: Fri, 10 Feb 2023 10:31:23 -0700 [thread overview]
Message-ID: <87bkm1xw9g.fsf@tromey.com> (raw)
In-Reply-To: <20230117163339.869534-1-simon.marchi@efficios.com> (Simon Marchi via Gdb-patches's message of "Tue, 17 Jan 2023 11:33:39 -0500")
>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
Simon> Fix this by splitting the gdb_test_multiple in two. The first one
Simon> expects the "Continuing with signal SIGINT" from the top GDB. The
Simon> second one expect "Quit" and the "(xgdb)" prompt from
Simon> $inferior_spawn_id. When debugging natively, this spawn id will be the
Simon> same as the top GDB's spawn id, but it's different when debugging with
Simon> GDBserver.
Did this go in? It looks reasonable to me FWIW.
Tom
next prev parent reply other threads:[~2023-02-10 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 16:33 Simon Marchi
2023-02-10 17:31 ` Tom Tromey [this message]
2023-02-10 18:56 ` Simon Marchi
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=87bkm1xw9g.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.com \
--cc=simon.marchi@polymtl.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).