From: Sandra Loosemore <sandra@codesourcery.com>
To: <gdb-patches@sourceware.org>
Cc: <tom@tromey.com>
Subject: [PATCH V2 0/5] gdb/testsuite: Miscelleanous fixes
Date: Sun, 23 Apr 2023 13:31:54 -0600 [thread overview]
Message-ID: <20230423193159.576300-1-sandra@codesourcery.com> (raw)
Reposting this series, which now incorporates minor tweaks suggested by
Tom Tromey to parts 2, 3, and 4. Parts 1 and 5 are unchanged.
OK for trunk?
-Sandra
Sandra Loosemore (5):
gdb/testsuite: Fix style.exp failures on targets without argc/argv
support
gdb/testsuite: Fix style.exp failures on targets without libopcodes
styling
gdb/testsuite: Adjust some testcases to allow Windows pathnames
gdb/testsuite: Disable some tests that are broken on remote Windows
host
gdb/testsuite: Make hook-stop.exp ignore termination message from GDB
stub
gdb/testsuite/gdb.base/bad-file.exp | 3 ++
gdb/testsuite/gdb.base/early-init-file.exp | 3 ++
.../gdb.base/empty-host-env-vars.exp | 3 ++
gdb/testsuite/gdb.base/hook-stop.exp | 2 +-
.../maint-expand-symbols-header-file.exp | 4 +-
gdb/testsuite/gdb.base/setshow.exp | 17 +++++--
gdb/testsuite/gdb.base/style.exp | 49 ++++++++++++++++---
gdb/testsuite/gdb.dwarf2/dw2-filename.exp | 2 +-
gdb/testsuite/gdb.mi/mi-info-sources.exp | 32 ++++++------
9 files changed, 86 insertions(+), 29 deletions(-)
--
2.31.1
next reply other threads:[~2023-04-23 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 19:31 Sandra Loosemore [this message]
2023-04-23 19:31 ` [PATCH V2 1/5] gdb/testsuite: Fix style.exp failures on targets without argc/argv support Sandra Loosemore
2023-04-23 19:31 ` [PATCH V2 2/5] gdb/testsuite: Fix style.exp failures on targets without libopcodes styling Sandra Loosemore
2023-04-23 19:31 ` [PATCH V2 3/5] gdb/testsuite: Adjust some testcases to allow Windows pathnames Sandra Loosemore
2023-04-24 17:16 ` [PATCH V2 0/5] gdb/testsuite: Miscelleanous 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=20230423193159.576300-1-sandra@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).