From: Nick Roberts <nick@nick.uklinux.net>
To: gdb@sources.redhat.com
Subject: MI command -stack-list-locals
Date: Thu, 06 Nov 2003 21:11:00 -0000 [thread overview]
Message-ID: <16298.50534.258926.575817@nick.uklinux.net> (raw)
As part of the transition from annotations to GDB/MI in Emacs, I would like
to extend the MI command -stack-list-locals.
Insight appears to display watch expressions and local variables in the same
way, where the values of arrays and structures can be expanded or contracted
with a mouse click. Perhaps it creates variable objects for both. GDB/MI,
however, either prints just the names of the locals, or their names and all
of their values i.e. entire structures and arrays. This can be a nuisance
with large arrays or structures and I would like to extend -stack-list-locals
to do the following:
1) Display the name and value for simple data types.
2) Display the name and type for complex data types.
e.g with the local variables:
int i, m[10];
struct {
int j;
int k;
} values;
the output for "-stack-list-locals 2", say, would be:
^done,locals=[{name="i",value="5"},
{name="m",type="int [10]"}
{name="values",type="struct {...}"}]
Then the user could examine an array or structure in more detail by creating a
variable object for it (through a mouse click on its name). Currently, I use
the speedbar for watch expressions and Emacs only allows there to be one. This
means that watch expressions and (expanded/contracted) local variables must
share it.
As this modification to -stack-list-locals won't be easy for me to implement,
I am looking for some reassurance that such a change, subject to the usual
requirements, would be accepted.
Nick http://www.nick.uklinux.net
next reply other threads:[~2003-11-06 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-06 21:11 Nick Roberts [this message]
2003-11-14 0:19 ` Jason Molenda
2003-11-14 23:17 ` Nick Roberts
2003-11-17 20:39 ` Alain Magloire
2003-11-17 21:12 ` Jason Molenda
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=16298.50534.258926.575817@nick.uklinux.net \
--to=nick@nick.uklinux.net \
--cc=gdb@sources.redhat.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