From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 0/8] TUI testing
Date: Fri, 26 Jul 2019 18:51:00 -0000 [thread overview]
Message-ID: <20190726185134.1856-1-tom@tromey.com> (raw)
Here's v2 of the TUI testing series.
This version uses gdb_assert in almost every place that was explicitly
calling pass and fail.
Tom
next reply other threads:[~2019-07-26 18:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 18:51 Tom Tromey [this message]
2019-07-26 18:51 ` [PATCH v2 2/8] Add test for "layout asm" Tom Tromey
2019-07-26 18:51 ` [PATCH v2 7/8] Add test case for empty TUI windows Tom Tromey
2019-07-26 18:51 ` [PATCH v2 5/8] Add TUI test for "list" Tom Tromey
2019-07-26 18:51 ` [PATCH v2 8/8] Add test that "file" shows "main" Tom Tromey
2019-07-26 18:51 ` [PATCH v2 1/8] A virtual terminal for the test suite Tom Tromey
2019-07-27 16:01 ` Andrew Burgess
2019-07-28 2:56 ` Tom Tromey
2019-07-31 15:44 ` minimal tcl version for gdb " Tom de Vries
2019-07-31 17:46 ` Tom Tromey
2019-08-01 9:39 ` Tom de Vries
2019-08-01 15:48 ` Tom Tromey
2019-07-26 18:51 ` [PATCH v2 4/8] Add TUI register window test Tom Tromey
2019-07-26 18:51 ` [PATCH v2 3/8] Add "layout split" test Tom Tromey
2019-07-26 18:51 ` [PATCH v2 6/8] Add TUI resizing test 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=20190726185134.1856-1-tom@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