public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "hlin117 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/17849] New: Showing local variables in gdb tui window
Date: Sat, 17 Jan 2015 17:41:00 -0000 [thread overview]
Message-ID: <bug-17849-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=17849
Bug ID: 17849
Summary: Showing local variables in gdb tui window
Product: gdb
Version: unknown
Status: NEW
Severity: enhancement
Priority: P2
Component: tui
Assignee: unassigned at sourceware dot org
Reporter: hlin117 at gmail dot com
Created attachment 8068
--> https://sourceware.org/bugzilla/attachment.cgi?id=8068&action=edit
An image of lldb's gui, while a program is running.
In gdb, a user could input `info locals` to show the current local variables,
but it would be convenient if in tui mode, we could see the local variables in
a separate window.
Furthermore, it would be convenient if a user could see the attributes of an
object, if an object is a local variable.
lldb somewhat already implements this feature, when you run lldb's gui. lldb's
gui is not officially documented, nor is it the main focus of lldb's
production. However, some of the functionality is there, and it would be nice
if gdb implemented this functionality as well.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-01-17 17:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-17 17:41 hlin117 at gmail dot com [this message]
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
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@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).