From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/4] More uses of require
Date: Fri, 24 Feb 2023 13:28:27 -0700 [thread overview]
Message-ID: <20230224-submit-require-fixes-v1-0-7cbcbbf613c9@tromey.com> (raw)
I found some more places that can use 'require'. Before this series,
some spots used "untested", some used "verbose", and some silently
returned. I think it's better for the tests to try to be consistent
in this sort of thing.
Tom
---
Tom Tromey (4):
Use require with target_info
Use require with gdb_skip_stdio_test
More uses of require with istarget
Use require with test_compiler_info
gdb/testsuite/gdb.base/a2-run.exp | 4 +---
gdb/testsuite/gdb.base/args.exp | 4 +---
gdb/testsuite/gdb.base/bp-cmds-continue-ctrl-c.exp | 10 ++--------
gdb/testsuite/gdb.base/branch-to-self.exp | 5 +----
gdb/testsuite/gdb.base/call-ar-st.exp | 5 +----
gdb/testsuite/gdb.base/call-rt-st.exp | 11 +++--------
gdb/testsuite/gdb.base/call-sc.exp | 5 +----
gdb/testsuite/gdb.base/call-signal-resume.exp | 16 +++++-----------
gdb/testsuite/gdb.base/call-strs.exp | 5 +----
gdb/testsuite/gdb.base/callexit.exp | 5 +----
gdb/testsuite/gdb.base/callfuncs.exp | 5 +----
gdb/testsuite/gdb.base/cast-call.exp | 5 +----
gdb/testsuite/gdb.base/catch-gdb-caused-signals.exp | 5 +----
gdb/testsuite/gdb.base/catch-signal-fork.exp | 5 +----
gdb/testsuite/gdb.base/catch-signal-siginfo-cond.exp | 5 +----
gdb/testsuite/gdb.base/catch-signal.exp | 5 +----
gdb/testsuite/gdb.base/checkpoint.exp | 4 +---
gdb/testsuite/gdb.base/exitsignal.exp | 5 +----
gdb/testsuite/gdb.base/fileio.exp | 5 +----
gdb/testsuite/gdb.base/foll-exec-mode.exp | 4 +---
gdb/testsuite/gdb.base/foll-exec.exp | 4 +---
gdb/testsuite/gdb.base/huge.exp | 4 +---
gdb/testsuite/gdb.base/infcall-input.exp | 5 +----
gdb/testsuite/gdb.base/inferior-args.exp | 5 +----
gdb/testsuite/gdb.base/inferior-died.exp | 5 +----
gdb/testsuite/gdb.base/interrupt-daemon-attach.exp | 10 ++--------
gdb/testsuite/gdb.base/interrupt.exp | 10 ++--------
gdb/testsuite/gdb.base/jit-reader-exec.exp | 4 +---
gdb/testsuite/gdb.base/kill-after-signal.exp | 5 +----
gdb/testsuite/gdb.base/long-inferior-output.exp | 5 +----
gdb/testsuite/gdb.base/long_long.exp | 4 +---
gdb/testsuite/gdb.base/multi-forks.exp | 4 +---
gdb/testsuite/gdb.base/paginate-after-ctrl-c-running.exp | 5 +----
gdb/testsuite/gdb.base/pie-execl.exp | 4 +---
gdb/testsuite/gdb.base/random-signal.exp | 10 ++--------
gdb/testsuite/gdb.base/relativedebug.exp | 5 +----
gdb/testsuite/gdb.base/savedregs.exp | 5 +----
gdb/testsuite/gdb.base/sigall.exp | 5 +----
gdb/testsuite/gdb.base/sigaltstack.exp | 5 +----
gdb/testsuite/gdb.base/sigbpt.exp | 5 +----
gdb/testsuite/gdb.base/sigchld.exp | 5 +----
gdb/testsuite/gdb.base/siginfo-addr.exp | 5 +----
gdb/testsuite/gdb.base/siginfo-infcall.exp | 5 +----
gdb/testsuite/gdb.base/siginfo-obj.exp | 5 +----
gdb/testsuite/gdb.base/siginfo-thread.exp | 5 +----
gdb/testsuite/gdb.base/siginfo.exp | 5 +----
gdb/testsuite/gdb.base/signals.exp | 5 +----
gdb/testsuite/gdb.base/signest.exp | 5 +----
gdb/testsuite/gdb.base/signull.exp | 5 +----
gdb/testsuite/gdb.base/sigrepeat.exp | 5 +----
gdb/testsuite/gdb.base/sigstep.exp | 5 +----
gdb/testsuite/gdb.base/sigwinch-notty.exp | 5 +----
gdb/testsuite/gdb.base/step-indirect-call-thunk.exp | 4 +---
gdb/testsuite/gdb.base/structs.exp | 5 +----
gdb/testsuite/gdb.base/unwindonsignal.exp | 10 ++--------
gdb/testsuite/gdb.base/vla-struct-fields.exp | 5 +----
gdb/testsuite/gdb.base/watch-cond-infcall.exp | 5 +----
gdb/testsuite/gdb.cp/gdb2495.exp | 10 ++--------
gdb/testsuite/gdb.fortran/array-slices.exp | 4 +---
gdb/testsuite/gdb.fortran/lbound-ubound.exp | 8 +++-----
gdb/testsuite/gdb.gdb/python-helper.exp | 5 +----
gdb/testsuite/gdb.mi/mi-syn-frame.exp | 5 +----
gdb/testsuite/gdb.mi/mi-threads-interrupt.exp | 5 +----
gdb/testsuite/gdb.reverse/sigall-precsave.exp | 5 +----
gdb/testsuite/gdb.reverse/sigall-reverse.exp | 5 +----
gdb/testsuite/gdb.server/reconnect-ctrl-c.exp | 5 +----
gdb/testsuite/gdb.threads/check-libthread-db.exp | 3 ++-
gdb/testsuite/gdb.threads/continue-pending-status.exp | 5 +----
gdb/testsuite/gdb.threads/hand-call-in-threads.exp | 11 ++++-------
gdb/testsuite/gdb.threads/interrupted-hand-call.exp | 11 ++++-------
gdb/testsuite/gdb.threads/leader-exit.exp | 5 +----
gdb/testsuite/gdb.threads/manythreads.exp | 5 +----
gdb/testsuite/gdb.threads/multiple-step-overs.exp | 5 +----
gdb/testsuite/gdb.threads/names.exp | 4 +---
gdb/testsuite/gdb.threads/non-stop-fair-events.exp | 5 +----
gdb/testsuite/gdb.threads/pthreads.exp | 5 +----
gdb/testsuite/gdb.threads/schedlock.exp | 5 +----
.../gdb.threads/signal-command-handle-nopass.exp | 5 +----
.../signal-command-multiple-signals-pending.exp | 5 +----
.../gdb.threads/signal-delivered-right-thread.exp | 5 +----
gdb/testsuite/gdb.threads/signal-sigtrap.exp | 5 +----
.../signal-while-stepping-over-bp-other-thread.exp | 5 +----
gdb/testsuite/gdb.threads/sigthread.exp | 9 +++------
gdb/testsuite/gdb.threads/thread-unwindonsignal.exp | 11 ++++-------
gdb/testsuite/gdb.trace/signal.exp | 5 +----
gdb/testsuite/gdb.tui/completion.exp | 4 +---
86 files changed, 112 insertions(+), 374 deletions(-)
---
base-commit: 1293ecd838c82e86f6c81d4518f5c662f8eaa0b9
change-id: 20230224-submit-require-fixes-68ce89de08be
Best regards,
--
Tom Tromey <tom@tromey.com>
next reply other threads:[~2023-02-24 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 20:28 Tom Tromey [this message]
2023-02-24 20:28 ` [PATCH 1/4] Use require with target_info Tom Tromey
2023-02-24 20:28 ` [PATCH 2/4] Use require with gdb_skip_stdio_test Tom Tromey
2023-02-24 20:28 ` [PATCH 3/4] More uses of require with istarget Tom Tromey
2023-02-24 20:28 ` [PATCH 4/4] Use require with test_compiler_info Tom Tromey
2023-03-10 14:56 ` [PATCH 0/4] More uses of require 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=20230224-submit-require-fixes-v1-0-7cbcbbf613c9@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
/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).