public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/28437] Internal error with `fs status` followed by `fs next`
Date: Sun, 12 Feb 2023 19:57:55 +0000 [thread overview]
Message-ID: <bug-28437-4717-pnR6UA0lbz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28437-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28437
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |14.1
Resolution|--- |FIXED
CC| |tromey at sourceware dot org
Status|UNCONFIRMED |RESOLVED
--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
> (gdb) fs status
> Focus set to status window.
I think this was fixed by:
commit 24f3aded1d42f515527e2de7e8e9e26f0b77c932
Author: Andrew Burgess <aburgess@redhat.com>
Date: Tue Dec 20 15:01:29 2022 +0000
gdb/testsuite/tui: more testing of the 'focus' command
I noticed that we didn't have many tests of the tui 'focus' command,
so I started adding some. This exposed a bug in GDB; we are able to
focus windows that should not be focusable, e.g. the 'status' window.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-12 19:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 0:37 [Bug tui/28437] New: `fs status` followed by `fs next` fails to switch focus on Mac sourceware at fastmail dot com
2021-10-09 1:45 ` [Bug tui/28437] Internal error with `fs status` followed by `fs next` simark at simark dot ca
2021-10-09 1:46 ` simark at simark dot ca
2021-10-09 1:53 ` sourceware at fastmail dot com
2023-02-12 19:57 ` tromey at sourceware dot org [this message]
2023-02-15 9:27 ` free_software at fastmail dot com
2023-02-15 9:40 ` free_software at fastmail dot com
2023-02-15 21:42 ` tromey at sourceware dot org
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=bug-28437-4717-pnR6UA0lbz@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).