From: Tom Tromey <tom@tromey.com>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH V3 4/4] gdb/testsuite: Make hook-stop.exp ignore termination message from GDB stub
Date: Tue, 05 Sep 2023 10:55:20 -0600 [thread overview]
Message-ID: <87tts8mufb.fsf@tromey.com> (raw)
In-Reply-To: <20230901032230.4193511-5-sandra@codesourcery.com> (Sandra Loosemore's message of "Thu, 31 Aug 2023 21:22:30 -0600")
Sandra> When a GDB stub is run via "target remote |", it sometimes produces
Sandra> extra output that ends up mixed with GDB's own output. For example,
Sandra> QEMU's built-in GDB stub responds to the vKill packet by printing
Sandra> nios2-elf-qemu-system: QEMU: Terminated via GDBstub
Sandra> before exiting.
If you have target boards that set up & invoke qemu, I think that would
be pretty interesting to have in-tree.
Tom
next prev parent reply other threads:[~2023-09-05 19:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 3:22 [PATCH V3 0/4] gdb/testsuite: Miscellaneous fixes Sandra Loosemore
2023-09-01 3:22 ` [PATCH V3 1/4] gdb/testsuite: Fix style.exp failures on targets without argc/argv support Sandra Loosemore
2023-09-01 3:22 ` [PATCH V3 2/4] gdb/testsuite: Adjust some testcases to allow Windows pathnames Sandra Loosemore
2023-09-01 3:22 ` [PATCH V3 3/4] gdb/testsuite: Disable some tests that are broken on remote Windows host Sandra Loosemore
2023-09-01 3:22 ` [PATCH V3 4/4] gdb/testsuite: Make hook-stop.exp ignore termination message from GDB stub Sandra Loosemore
2023-09-05 16:55 ` Tom Tromey [this message]
2023-09-05 16:54 ` [PATCH V3 0/4] gdb/testsuite: Miscellaneous fixes 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=87tts8mufb.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=sandra@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).