From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: [PATCH 00/14] Break up gdb.base/break.exp in multiple procs
Date: Wed, 23 Nov 2022 13:39:45 -0500 [thread overview]
Message-ID: <20221123183959.2476477-1-simon.marchi@polymtl.ca> (raw)
The test gdb.base/break.exp feels like a big house of cards that will
crumble the second you touch it. It is very long and it's really not
clear which test depends on the state left by which previous test. This
series aims at making it more manageable by breaking it up into many
procs, each starting with a fresh GDB. So you can be confident that the
tests in a proc only depends on the state of GDB resulting of other
tests in the same proc.
Simon Marchi (14):
gdb/testsuite/gdb.base/break.exp: split test_break_commands_clear
gdb/testsuite/gdb.base/break.exp: split
test_break_file_line_convenience_var
gdb/testsuite/gdb.base/break.exp: split test_rbreak_shlib
gdb/testsuite/gdb.base/break.exp: split test_break_optimized_prologue
gdb/testsuite/gdb.base/break.exp: use proc_with_prefix for
test_next_with_recursion
gdb/testsuite/gdb.base/break.exp: split test_finish_arguments
gdb/testsuite/gdb.base/break.exp: split test_break_user_call
gdb/testsuite/gdb.base/break.exp: split
test_break_line_convenience_var
gdb/testsuite/gdb.base/break.exp: split test_break_silent_and_more
gdb/testsuite/gdb.base/break.exp: split test_break_default
gdb/testsuite/gdb.base/break.exp: split test_break_nonexistent_line
gdb/testsuite/gdb.base/break.exp: split test_no_break_on_catchpoint
gdb/testsuite/gdb.base/break.exp: split test_tbreak
gdb/testsuite/gdb.base/break.exp: split test_break
gdb/testsuite/gdb.base/break.exp | 1191 +++++++++++++++---------------
1 file changed, 615 insertions(+), 576 deletions(-)
base-commit: 8db533e7d6d28db1be0ae4c95ddea7aa3a6224c8
--
2.38.1
next reply other threads:[~2022-11-23 18:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 18:39 Simon Marchi [this message]
2022-11-23 18:39 ` [PATCH 01/14] gdb/testsuite/gdb.base/break.exp: split test_break_commands_clear Simon Marchi
2022-11-23 18:39 ` [PATCH 02/14] gdb/testsuite/gdb.base/break.exp: split test_break_file_line_convenience_var Simon Marchi
2022-11-23 18:39 ` [PATCH 03/14] gdb/testsuite/gdb.base/break.exp: split test_rbreak_shlib Simon Marchi
2022-11-23 18:39 ` [PATCH 04/14] gdb/testsuite/gdb.base/break.exp: split test_break_optimized_prologue Simon Marchi
2022-11-23 18:39 ` [PATCH 05/14] gdb/testsuite/gdb.base/break.exp: use proc_with_prefix for test_next_with_recursion Simon Marchi
2022-11-23 18:39 ` [PATCH 06/14] gdb/testsuite/gdb.base/break.exp: split test_finish_arguments Simon Marchi
2022-11-23 18:39 ` [PATCH 07/14] gdb/testsuite/gdb.base/break.exp: split test_break_user_call Simon Marchi
2022-11-23 18:39 ` [PATCH 08/14] gdb/testsuite/gdb.base/break.exp: split test_break_line_convenience_var Simon Marchi
2022-11-23 18:39 ` [PATCH 09/14] gdb/testsuite/gdb.base/break.exp: split test_break_silent_and_more Simon Marchi
2022-11-23 18:39 ` [PATCH 10/14] gdb/testsuite/gdb.base/break.exp: split test_break_default Simon Marchi
2022-11-23 18:39 ` [PATCH 11/14] gdb/testsuite/gdb.base/break.exp: split test_break_nonexistent_line Simon Marchi
2022-11-23 18:39 ` [PATCH 12/14] gdb/testsuite/gdb.base/break.exp: split test_no_break_on_catchpoint Simon Marchi
2022-11-23 18:39 ` [PATCH 13/14] gdb/testsuite/gdb.base/break.exp: split test_tbreak Simon Marchi
2022-11-23 18:39 ` [PATCH 14/14] gdb/testsuite/gdb.base/break.exp: split test_break Simon Marchi
2022-11-24 3:03 ` [PATCH 00/14] Break up gdb.base/break.exp in multiple procs Kevin Buettner
2022-11-24 15:14 ` Simon Marchi
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=20221123183959.2476477-1-simon.marchi@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--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).