From: Nick Roberts <nickrob@snap.net.nz>
To: "André Pönitz" <apoenitz@trolltech.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Type information in -data-evaluate-expression
Date: Mon, 30 Jul 2007 23:17:00 -0000 [thread overview]
Message-ID: <18094.22832.139526.843547@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200707301733.59718.apoenitz@trolltech.com>
> > What is the use case where you need to just get the type of an expression,
> > without doing anything with it?
>
> One use case would be to display values in a graphical frontend
> when hovering (or even moving) the mouse over some expression.
> My current "best practice" here is to create a variable called "tooltip",
> extract value and type and delete it again, only to create it again
> with a slightly different expression etc. So I need two roundtrips
> and need some syncronization to handle the two partial results
> whereas the proposed "enhanced" version would allow a simple
> hit-and-run implementation...
What happens if you have compiled with "-g3", have the line
#define STOP abort ()
in your code and the mouse hovers over STOP?
Also do the values of large arrays/structures appear as large tooltips?
Around the end of last year there was a discussion on gdb-patches (Re: variable
objects and registers) about using variable objects for tooltips. Jim
Ingham said that Apple currently do this for Xcode and it works well. I think
we should explore this possibility and perhaps review their code.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2007-07-30 21:33 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
2007-07-30 17:06 ` André Pönitz
2007-07-30 23:17 ` Nick Roberts [this message]
[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=18094.22832.139526.843547@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=apoenitz@trolltech.com \
--cc=gdb-patches@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