From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: Re: Type information in -data-evaluate-expression
Date: Mon, 30 Jul 2007 15:34:00 -0000 [thread overview]
Message-ID: <f8kqea$dk$1@sea.gmane.org> (raw)
In-Reply-To: <200707301540.59361.apoenitz@trolltech.com>
André Pönitz wrote:
>
> Hi all.
>
> While playing around with gdb's "mi" interface (which looks rather
> nice for scripting btw...) I came across a few places where I think
> the interface might be made even more convienient without much
> effort.
>
> One example: As far as I can see currently the only way to obtain
> the type of an expression is to use -var-create & -var-delete.
> It would be more convienient for me if I could get that information
> with a single command without creating a variable which will be
> thrown away immediatedly afterwards.
What is the use case where you need to just get the type of an expression,
without doing anything with it?
> A possibility to do so would be to "enhance" "-data-evaluate-expression"
> to return not only the value, but also the type information which is
> is available after the evaluation process anyway.
>
> I came up with a tiny patch that "seem to work for me". But as this
> is the first time I look gdb source I am unsure whether this is done
> properly or if some kind of cleanup is needed, and, of course, whether
> there is a chance to get such patches included in gdb proper
> at some point of time.
I'd expect this patch will break a bunch of tests, since those tests
are not expecting the additional 'type' field. The patch itself
seems reasonable as far as code is concerned, but I'm not yet sure about
your use case. I'd prefer -data-evaluate-expression to fall to misuse,
rather than adding some new functionality to it.
- Volodya
next prev parent reply other threads:[~2007-07-30 13:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 13:52 André Pönitz
2007-07-30 15:34 ` Vladimir Prus [this message]
2007-07-30 17:06 ` André Pönitz
2007-07-30 23:17 ` Nick Roberts
[not found] ` <200707310922.14919.apoenitz@trolltech.com>
2007-07-31 9:13 ` Nick Roberts
2007-07-31 9:40 ` André Pönitz
2007-07-31 10:39 ` Nick Roberts
2007-07-31 11:02 ` Vladimir Prus
2007-07-31 11:25 ` Nick Roberts
2007-07-31 11:06 ` Daniel Jacobowitz
2007-07-31 13:35 ` Nick Roberts
2007-07-31 10:14 ` Vladimir Prus
2007-07-31 10:29 ` Nick Roberts
2007-07-31 8:09 ` Vladimir Prus
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='f8kqea$dk$1@sea.gmane.org' \
--to=ghost@cs.msu.su \
--cc=gdb-patches@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