public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Bruno Larsen <blarsen@redhat.com>
To: gdb-patches@sourceware.org
Cc: Bruno Larsen <blarsen@redhat.com>
Subject: [PATCH v2 0/4] Many fixes to gdb.reverse tests
Date: Thu, 27 Jul 2023 09:41:14 +0200	[thread overview]
Message-ID: <20230727074118.1583199-1-blarsen@redhat.com> (raw)
In-Reply-To: <20230725095833.236804-1-blarsen@redhat.com>

This patch series applies multiple simple fixes to tests in the
gdb.reverse subdirectory. Changes were tested with the base
configuration in x86_64, both with clang and gcc, and no regressions
were found.

With these changes, there are only 10 unexpected failures extra when
running the subdirectory with clang, all from finish-reverse-next.exp,
and all relating to the issues that Carl Love has been trying to solve
with reverse stepping in contiguous ranges.

Changes for v2:
 * Implemented Tromey's suggestions
 * Small change to get_hexadecimal_valueof - added nopass option

Bruno Larsen (4):
  gdb/testsuite: Fix many errors in gdb.reverse with clang
  gdb/testsuite: fix gdb.reverse/solib-*.exp tests when using clang
  gdb/testsuite: fix testing gdb.reverse/step-reverse.exp with clang
  gdb/testsuite: Multiple improvements for gdb.reverse/insn-reverse.exp

 gdb/testsuite/gdb.reverse/break-reverse.c    |   4 +-
 gdb/testsuite/gdb.reverse/finish-reverse.c   |   4 +-
 gdb/testsuite/gdb.reverse/insn-reverse-x86.c | 324 +++++++++----------
 gdb/testsuite/gdb.reverse/insn-reverse.exp   |   4 +-
 gdb/testsuite/gdb.reverse/shr2.c             |   3 +-
 gdb/testsuite/gdb.reverse/solib-precsave.exp |  24 +-
 gdb/testsuite/gdb.reverse/solib-reverse.c    |   5 +-
 gdb/testsuite/gdb.reverse/solib-reverse.exp  |  24 +-
 gdb/testsuite/gdb.reverse/step-precsave.exp  |  18 +-
 gdb/testsuite/gdb.reverse/step-reverse.exp   |  20 +-
 gdb/testsuite/gdb.reverse/watch-reverse.c    |   4 +-
 gdb/testsuite/lib/gdb.exp                    |  12 +-
 12 files changed, 259 insertions(+), 187 deletions(-)

-- 
2.41.0


  parent reply	other threads:[~2023-07-27  7:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25  9:58 [PATCH " Bruno Larsen
2023-07-25  9:58 ` [PATCH 1/4] gdb/testsuite: Fix many errors in gdb.reverse with clang Bruno Larsen
2023-07-25  9:58 ` [PATCH 2/4] gdb/testsuite: fix gdb.reverse/solib-*.exp tests when using clang Bruno Larsen
2023-07-26 13:37   ` Tom Tromey
2023-07-25  9:58 ` [PATCH 3/4] gdb/testsuite: fix testing gdb.reverse/step-reverse.exp with clang Bruno Larsen
2023-07-26 13:39   ` Tom Tromey
2023-07-25  9:58 ` [PATCH 4/4] gdb/testsuite: Multiple improvements for gdb.reverse/insn-reverse.exp Bruno Larsen
2023-07-27  7:41 ` Bruno Larsen [this message]
2023-07-27  7:41   ` [PATCH v2 1/4] gdb/testsuite: Fix many errors in gdb.reverse with clang Bruno Larsen
2023-07-27  7:41   ` [PATCH v2 2/4] gdb/testsuite: fix gdb.reverse/solib-*.exp tests when using clang Bruno Larsen
2023-07-27  7:41   ` [PATCH v2 3/4] gdb/testsuite: fix testing gdb.reverse/step-reverse.exp with clang Bruno Larsen
2023-07-28 13:14     ` Tom Tromey
2023-07-28 13:20       ` Bruno Larsen
2023-07-28 14:18         ` Tom Tromey
2023-07-28 14:20           ` Bruno Larsen
2023-07-27  7:41   ` [PATCH v2 4/4] gdb/testsuite: Multiple improvements for gdb.reverse/insn-reverse.exp Bruno Larsen

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=20230727074118.1583199-1-blarsen@redhat.com \
    --to=blarsen@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).