From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/3] [gdb/tui] Allow second tui enable if first fails
Date: Wed, 29 Apr 2026 13:13:22 +0200 [thread overview]
Message-ID: <20260429111325.1600061-1-tdevries@suse.de> (raw)
Commit fb23d7ba4a2 ("[gdb/tui] Handle error in tui_enable") handles a
particular error during tui_enable, but doesn't allow trying to enable TUI
again.
This patch series fixes that.
The first two patches do some refactoring.
The third patch contains the fix.
Tom de Vries (3):
[gdb/tui] Factor out require_tui_terminal
[gdb/tui] Factor out init_ncurses
[gdb/tui] Allow second tui enable if first fails
gdb/tui/tui.c | 104 +++++++++++++++++++++++++++++++++-----------------
1 file changed, 68 insertions(+), 36 deletions(-)
base-commit: 8a5e138e6276ce7644ab858751440cb59f35623b
--
2.51.0
next reply other threads:[~2026-04-29 11:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 11:13 Tom de Vries [this message]
2026-04-29 11:13 ` [PATCH 1/3] [gdb/tui] Factor out require_tui_terminal Tom de Vries
2026-04-29 11:13 ` [PATCH 2/3] [gdb/tui] Factor out init_ncurses Tom de Vries
2026-04-29 11:13 ` [PATCH 3/3] [gdb/tui] Allow second tui enable if first fails Tom de Vries
2026-05-01 19:06 ` Tom Tromey
2026-05-11 10:38 ` 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=20260429111325.1600061-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