public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "paulbuxton.mail at googlemail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/17849] Showing local variables in gdb tui window
Date: Sun, 18 Jun 2023 06:59:44 +0000 [thread overview]
Message-ID: <bug-17849-4717-kcDbTJeKzw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17849-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17849
--- Comment #11 from Paul Buxton <paulbuxton.mail at googlemail dot com> ---
I had stopped looking as I thought Hannes patch covered the functionality
already. I will try and have a look in the next week or so.
On Sat, Jun 17, 2023 at 6:41 PM tromey at sourceware dot org <
sourceware-bugzilla@sourceware.org> wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=17849
>
> --- Comment #10 from Tom Tromey <tromey at sourceware dot org> ---
> What's the state of this patch?
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-06-18 6:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-17 17:41 [Bug tui/17849] New: " hlin117 at gmail dot com
2015-07-02 14:11 ` [Bug tui/17849] " palves at redhat dot com
2021-03-14 17:44 ` paulbuxton.mail at googlemail dot com
2021-03-14 18:53 ` tromey at sourceware dot org
2021-03-15 7:56 ` paulbuxton.mail at googlemail dot com
2021-03-17 17:11 ` ssbssa at sourceware dot org
2023-06-17 17:41 ` tromey at sourceware dot org
2023-06-18 6:59 ` paulbuxton.mail at googlemail dot com [this message]
2023-11-03 17:52 ` paulbuxton.mail at googlemail dot com
2023-11-11 16:41 ` tromey at sourceware dot org
2023-11-11 22:45 ` ssbssa 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-17849-4717-kcDbTJeKzw@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).