From: Daniel Jacobowitz <drow@false.org>
To: Greg Watson <g.watson@computer.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: more detailed type information
Date: Tue, 28 Mar 2006 23:50:00 -0000 [thread overview]
Message-ID: <20060328223609.GD11817@nevyn.them.org> (raw)
In-Reply-To: <A5CB13EC-09DC-41C3-80E1-87F215154C54@computer.org>
On Thu, Mar 09, 2006 at 12:49:23PM -0700, Greg Watson wrote:
> I'm using Eclipse as a front-end for gdb, but I need to be able to
> get more detailed type information than is currently possible. This
> is required in order to provide more sophisticated functionality than
> just displaying the type and value as strings.
Hi Greg,
Can you be a little more detailed about what you need from GDB?
There've been several mentions of this functionality recently,
and I'm nearly positive that Apple's GDB supports something similar,
so it's clearly a good idea. However, what you have is a very thin
layer around GDB's type system, which makes it hard to change the type
system at all without simultaneously changing the MI interface. I'd
like to know what information is really useful.
With C, of course, it doesn't much matter: the underlying type system
can be simple because the language type system is simple. But with
other supported languages this can be much harder.
And, no offense, but the ref=/seen= interface is nasty! Maybe we
should give types session UIDs.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-28 22:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 20:20 Greg Watson
2006-03-28 23:50 ` Daniel Jacobowitz [this message]
2006-03-29 0:20 ` Greg Watson
2006-03-29 0:54 ` Greg Watson
2006-04-06 6:34 ` 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=20060328223609.GD11817@nevyn.them.org \
--to=drow@false.org \
--cc=g.watson@computer.org \
--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