From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: The 'x' command: size problem
Date: Tue, 06 Sep 2005 15:25:00 -0000 [thread overview]
Message-ID: <20050906152448.GA2444@nevyn.them.org> (raw)
In-Reply-To: <dfkaub$n1c$1@sea.gmane.org>
On Tue, Sep 06, 2005 at 07:00:28PM +0400, Vladimir Prus wrote:
> works. In fact, the x_command function in printcmd.c expects the the size
> argument be always given as literal.
>
> This limitation makes it somewhat harder to implement "show this
> variable/expression in binary" command in a GUI. Are there any easy
> workarounds?
Not as far as I know. But you're in a GUI, i.e. hopefully something
with logic and capable of parsing GDB's responses. Is it really that
hard to get the size and print out the right bytes?
-data-evaluate-expression "sizeof(i)"
^done,value="4"
(gdb)
-data-read-memory "&i" t 1 1 4
^done,addr="0xbf82ec04",nr-bytes="4",total-bytes="4",next-row="0xbf82ec08",prev-row="0xbf82ec00",next-page="0xbf82ec08",prev-page="0xbf82ec00",memory=[{addr="0xbf82ec04",data=["10011100","01011110","11101111","10110111"]}]
(gdb)
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-09-06 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 15:04 Vladimir Prus
2005-09-06 15:25 ` Daniel Jacobowitz [this message]
2005-09-06 15:35 ` Vladimir Prus
2005-09-06 15:42 ` Daniel Jacobowitz
2005-09-07 6:55 ` Vladimir Prus
2005-09-07 13:14 ` Daniel Jacobowitz
2005-09-07 13:42 ` Vladimir Prus
2005-09-07 18:02 ` Eli Zaretskii
2005-09-06 19:17 ` Eli Zaretskii
2005-09-06 19:29 ` Daniel Jacobowitz
2005-09-07 6:40 ` Vladimir Prus
[not found] ` <17181.45190.337014.159288@gargle.gargle.HOWL>
2005-09-06 15:27 ` 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=20050906152448.GA2444@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).