From: Vladimir Prus <ghost@cs.msu.su>
To: gdb-patches@sources.redhat.com
Subject: Re: RFC: more detailed type information
Date: Thu, 06 Apr 2006 06:34:00 -0000 [thread overview]
Message-ID: <e12cp1$lsv$1@sea.gmane.org> (raw)
In-Reply-To: <1C1CE32A-A819-4150-B6E6-7F27120B2A92@computer.org>
Greg Watson wrote:
>>> 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.
> Just a quick followup. I've taken a look at the Apple changes to the
> MI code. It appears they have (amongst other things) added a
> 'typecode' value to the -var-create and -var-list-children commands.
> This typecode is a direct translation of the GDB typecode into a
> string (TYPE_CODE_ARRAY -> 'ARRAY', etc.), and would make it somewhat
> easier to obtain type information. It still necessitates many MI
> commands to obtain a complex type description, however, nor does it
> appear to be possible to obtain length and/or byte ordering information.
>
> The additional level of information provided by Apple would
> definitely be beneficial, but for my purposes a recursive type
> description would still be the most preferable way to go.
I, too, would like such detailed information to be available. In fact, I've
asked for this too:
http://sources.redhat.com/ml/gdb/2006-04/msg00016.html
Daniel, maybe you can follow up to that post of mine on main list, or
indicate what exactly do you want from this "MI type system" to be
accepted? As I understand, GDB type system is basically direct
representation of type system of languages it supports, so it's not likely
it will change any time soon.
- Volodya
prev parent reply other threads:[~2006-04-06 6:34 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
2006-03-29 0:20 ` Greg Watson
2006-03-29 0:54 ` Greg Watson
2006-04-06 6:34 ` Vladimir Prus [this message]
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='e12cp1$lsv$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