From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Language of registers
Date: Mon, 27 Nov 2006 07:37:00 -0000 [thread overview]
Message-ID: <uodqtz6p4.fsf@gnu.org> (raw)
In-Reply-To: <eke0pm$d8s$2@sea.gmane.org> (message from Vladimir Prus on Mon, 27 Nov 2006 09:32:09 +0300)
> From: Vladimir Prus <ghost@cs.msu.su>
> Date: Mon, 27 Nov 2006 09:32:09 +0300
> >
> > What advantage do variable objects offer for register names?
>
> To begin with -- consistenly. There is no fundamental difference between
> ordinary values and registers. The frontend knows how to display the
> hierarchy of variable objects, and there's no need to force the frontend to
> have additional logic for register. Note that Eclipse, for example, does
> create variable objects for all registers at the moment.
>
> The second advantage is that -data-list-register-values has no hierarchy at
> all. If you try
>
> -data-list-register-values xmm1
>
> then gdb print print half-screen of output that should be specially parsed
> and displayed. When using variable objects, the frontend already has the
> parsing/display code.
It would be nice to have these explanation in the manual...
Thanks.
next prev parent reply other threads:[~2006-11-27 7:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 0:43 Nick Roberts
2006-11-27 6:32 ` Vladimir Prus
2006-11-27 7:37 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-06 21:54 Nick Roberts
2006-12-06 22:03 ` Daniel Jacobowitz
2006-12-06 22:55 ` Nick Roberts
2006-12-06 23:10 ` Daniel Jacobowitz
2006-11-25 11:22 Vladimir Prus
2006-11-27 14:03 ` Daniel Jacobowitz
2006-11-28 17:12 ` Vladimir Prus
2006-11-28 17:23 ` Daniel Jacobowitz
2006-11-28 18:09 ` Vladimir Prus
2006-12-01 14:32 ` Daniel Jacobowitz
2006-12-01 18:03 ` Jim Ingham
2006-11-29 10:12 ` 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=uodqtz6p4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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