From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] [gdb/tui] Allow second tui enable if first fails
Date: Mon, 11 May 2026 12:38:50 +0200 [thread overview]
Message-ID: <519c8bad-ad4f-4f43-93a7-d14756aa174d@suse.de> (raw)
In-Reply-To: <87a4ujgda3.fsf@tromey.com>
On 5/1/26 9:06 PM, Tom Tromey wrote:
>>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
>
> Tom> Commit fb23d7ba4a2 ("[gdb/tui] Handle error in tui_enable") handles a
> Tom> particular error during tui_enable, but doesn't allow trying to enable TUI
> Tom> again.
>
> Tom> I tried to get this to work, but didn't manage because I didn't understand the
> Tom> interaction between endwin and the "tui_batch_rendering defer" destructor:
> Tom> - first endwin restores the shell terminal mode
> Tom> - then the defer destructor calls doupdate, restoring program shell mode.
>
> This is probably just an oversight in tui_batch_rendering and perhaps
> the destructor should check some other flag as well before calling doupdate.
Thanks for the suggestion, I've submitted a v2 that checks for
tui_active (
https://sourceware.org/pipermail/gdb-patches/2026-May/227293.html ).
Thanks,
- Tom
prev parent reply other threads:[~2026-05-11 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 11:13 [PATCH 0/3] " Tom de Vries
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 [this message]
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=519c8bad-ad4f-4f43-93a7-d14756aa174d@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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