From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [pushed 0/3] [gdb/testsuite] Add some tui test-cases
Date: Fri, 16 Oct 2026 17:28:46 +0200 [thread overview]
Message-ID: <20261016152849.87694-1-tdevries@suse.de> (raw)
I came across commit a4f8f290270 ("gdb/tui: disable tui mode when an assert
triggers"), and noticed that there are no test-cases that exercise this
scenario.
This series contains three patches.
The last two each add one such test-case. I've confirmed that the test-cases
fail if commit a4f8f290270 is reverted.
The first is a trivial fix in proc find_core_file, that is required for the
second patch.
Tested on x86_64-linux.
Tom de Vries (3):
[gdb/testsuite] Handle non-existing testfile in find_core_file
[gdb/testsuite] Add gdb.tui/fatal.exp
[gdb/testsuite] Add gdb.tui/internal-error.exp
gdb/testsuite/gdb.tui/fatal.exp | 71 ++++++++++++++++++++++++
gdb/testsuite/gdb.tui/internal-error.exp | 59 ++++++++++++++++++++
gdb/testsuite/lib/gdb.exp | 4 +-
3 files changed, 133 insertions(+), 1 deletion(-)
create mode 100644 gdb/testsuite/gdb.tui/fatal.exp
create mode 100644 gdb/testsuite/gdb.tui/internal-error.exp
base-commit: d5482742b2e597b2db086b0588a90feb22d10f68
--
2.51.0
next reply other threads:[~2026-10-16 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 15:28 Tom de Vries [this message]
2026-10-16 15:28 ` [pushed 1/3] [gdb/testsuite] Handle non-existing testfile in find_core_file Tom de Vries
2026-10-16 15:28 ` [pushed 2/3] [gdb/testsuite] Add gdb.tui/fatal.exp Tom de Vries
2026-10-16 15:28 ` [pushed 3/3] [gdb/testsuite] Add gdb.tui/internal-error.exp Tom de Vries
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=20261016152849.87694-1-tdevries@suse.de \
--to=tdevries@suse.de \
--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