public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/28600] "layout reg" nor "kill" refresh the TUI registers window
Date: Fri, 24 Nov 2023 10:28:12 +0000	[thread overview]
Message-ID: <bug-28600-4717-AURo8K0ziY@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28600-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28600

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vries at gcc dot gnu.org

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Pedro Alves from comment #0)
> If you run to main in CLI mode, and then issue 'layout reg', the register
> window shows:
> 
>   "[ Register Values Unavailable ]"
> 
> ... even though the process is live and we have a frame selected.
> 

https://sourceware.org/pipermail/gdb-patches/2023-November/204464.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2023-11-24 10:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17 19:17 [Bug tui/28600] New: " pedro at palves dot net
2023-11-24 10:28 ` vries at gcc dot gnu.org [this message]
2023-12-16  8:31 ` [Bug tui/28600] " cvs-commit at gcc dot gnu.org
2023-12-16  8:37 ` vries at gcc dot gnu.org
2023-12-17 19:37 ` tromey at sourceware dot org
2024-02-08 19:34 ` cvs-commit at gcc dot gnu.org
2024-02-08 19:36 ` 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-28600-4717-AURo8K0ziY@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).