public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/5] gdb/testsuite: stricter matching for gdb_test
Date: Fri, 31 Mar 2023 21:20:53 +0100	[thread overview]
Message-ID: <cover.1680293848.git.aburgess@redhat.com> (raw)

The goal of this series is to make the pattern matching in gdb_test
stricter with respect to end of line sequences.  This encourages us
all to be a little more precise when writting the output patterns for
use in gdb_test, but I think this is a good thing for GDB - our tests
will get a little stricter.

The final patch adds a new feature to gdb_test, a modified version of
the '^' anchor, which again, should (I hope) allow us to write
stricter output patterns, which I think is a good thing for GDB.

Thanks,
Andrew

---

Andrew Burgess (5):
  gdb/testsuite: fix occasional failure in
    gdb.base/clear_non_user_bp.exp
  gdb: remove some trailing newlines from warning messages
  gdb/testsuite: use 'return' in gdb_test_no_output
  gdb/testsuite: change newline patterns used in gdb_test
  gdb/testsuite: special case '^' in gdb_test pattern

 gdb/language.c                                |   8 +-
 gdb/remote.c                                  |   4 +-
 gdb/testsuite/gdb.ada/varsize_limit.exp       |   2 +-
 gdb/testsuite/gdb.arch/amd64-entry-value.exp  |  59 +++++++---
 .../gdb.arch/amd64-invalid-stack-middle.exp   |   4 +-
 .../gdb.arch/amd64-invalid-stack-top.exp      |   4 +-
 gdb/testsuite/gdb.base/call-rt-st.exp         |   2 +-
 gdb/testsuite/gdb.base/charset.exp            |   4 +-
 gdb/testsuite/gdb.base/clear_non_user_bp.exp  |   2 +-
 gdb/testsuite/gdb.base/compare-sections.exp   |   2 +-
 gdb/testsuite/gdb.base/default.exp            |   4 +-
 gdb/testsuite/gdb.base/display.exp            |  10 +-
 gdb/testsuite/gdb.base/foll-fork.exp          |   2 +-
 gdb/testsuite/gdb.base/fullpath-expand.exp    |   4 +-
 gdb/testsuite/gdb.base/info-macros.exp        |  12 +-
 .../gdb.base/multi-line-starts-subshell.exp   |   2 +-
 gdb/testsuite/gdb.base/new-ui-echo.exp        |   4 +-
 gdb/testsuite/gdb.base/new-ui.exp             |   6 +-
 gdb/testsuite/gdb.base/pc-fp.exp              |   2 +-
 gdb/testsuite/gdb.base/pending.exp            |   2 +-
 gdb/testsuite/gdb.base/rtld-step.exp          |   4 +-
 gdb/testsuite/gdb.base/setshow.exp            |   4 +-
 gdb/testsuite/gdb.base/settings.exp           |   9 +-
 gdb/testsuite/gdb.base/signals.exp            |   2 +-
 gdb/testsuite/gdb.base/until.exp              |   2 +-
 gdb/testsuite/gdb.base/watch-bitfields.exp    |   4 +-
 gdb/testsuite/gdb.base/watchpoint.exp         |  17 +--
 gdb/testsuite/gdb.base/with.exp               |  15 ++-
 .../gdb.base/wrong_frame_bt_full.exp          |   4 +-
 gdb/testsuite/gdb.btrace/buffer-size.exp      |   4 +-
 .../gdb.btrace/function_call_history.exp      |   2 +-
 .../gdb.btrace/instruction_history.exp        |  10 +-
 gdb/testsuite/gdb.btrace/record_goto.exp      |   8 +-
 .../gdb.cp/incomplete-type-overload.exp       |   2 +-
 gdb/testsuite/gdb.cp/maint.exp                |   8 +-
 gdb/testsuite/gdb.cp/ovldbreak.exp            |  14 +--
 gdb/testsuite/gdb.cp/userdef.exp              |  20 ++--
 gdb/testsuite/gdb.cp/virtfunc.exp             |  23 +++-
 gdb/testsuite/gdb.guile/scm-breakpoint.exp    |   2 +-
 gdb/testsuite/gdb.guile/scm-cmd.exp           |   2 +-
 gdb/testsuite/gdb.linespec/break-ask.exp      |   4 +-
 .../gdb.mi/user-selected-context-sync.exp     |   2 +-
 gdb/testsuite/gdb.opt/inline-break.exp        |   6 +-
 gdb/testsuite/gdb.python/py-breakpoint.exp    |   6 +-
 gdb/testsuite/gdb.python/py-framefilter.exp   |   2 +-
 gdb/testsuite/gdb.python/python.exp           |   2 +-
 .../gdb.reverse/machinestate-precsave.exp     |  60 +++++-----
 gdb/testsuite/gdb.reverse/machinestate.exp    |  60 +++++-----
 gdb/testsuite/gdb.stabs/exclfwd.exp           |   4 +-
 .../gdb.threads/foll-fork-other-thread.exp    |   2 +-
 gdb/testsuite/gdb.threads/gcore-thread.exp    |   4 +-
 gdb/testsuite/gdb.trace/actions.exp           | 109 +++++++++---------
 gdb/testsuite/gdb.trace/deltrace.exp          |  73 ++++++------
 gdb/testsuite/gdb.trace/infotrace.exp         |   6 +-
 gdb/testsuite/gdb.trace/passcount.exp         |   8 +-
 gdb/testsuite/gdb.trace/tracecmd.exp          |   8 +-
 gdb/testsuite/gdb.trace/while-stepping.exp    |   2 +-
 gdb/testsuite/lib/gdb.exp                     |  35 ++++--
 58 files changed, 385 insertions(+), 303 deletions(-)


base-commit: 3712e78cab09017bf59105d44e2f745c5e608c5a
-- 
2.25.4


             reply	other threads:[~2023-03-31 20:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 20:20 Andrew Burgess [this message]
2023-03-31 20:20 ` [PATCH 1/5] gdb/testsuite: fix occasional failure in gdb.base/clear_non_user_bp.exp Andrew Burgess
2023-03-31 20:20 ` [PATCH 2/5] gdb: remove some trailing newlines from warning messages Andrew Burgess
2023-03-31 20:20 ` [PATCH 3/5] gdb/testsuite: use 'return' in gdb_test_no_output Andrew Burgess
2023-03-31 20:20 ` [PATCH 4/5] gdb/testsuite: change newline patterns used in gdb_test Andrew Burgess
2023-04-27 19:39   ` Simon Marchi
2023-04-28 14:05     ` Andrew Burgess
2023-04-28 15:51     ` Andrew Burgess
2023-04-28 15:57       ` Simon Marchi
2023-04-28 18:37         ` Simon Marchi
2023-04-28 21:50           ` Andrew Burgess
2023-05-02 19:16             ` Simon Marchi
2023-04-29 15:20   ` Tom de Vries
2023-05-01 14:33     ` Andrew Burgess
2023-05-01 15:10       ` Tom de Vries
2023-05-02 11:13         ` Andrew Burgess
2023-05-02 14:48           ` Tom de Vries
2023-05-05 17:01             ` Andrew Burgess
2023-05-09  9:54               ` Andrew Burgess
2023-05-10  7:22                 ` Tom de Vries
2023-05-12 12:54                   ` Andrew Burgess
2023-03-31 20:20 ` [PATCH 5/5] gdb/testsuite: special case '^' in gdb_test pattern Andrew Burgess
2023-04-17 16:12 ` [PATCH 0/5] gdb/testsuite: stricter matching for gdb_test Tom Tromey
2023-04-27 12:58   ` Andrew Burgess

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=cover.1680293848.git.aburgess@redhat.com \
    --to=aburgess@redhat.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).