From: Vladimir Prus <ghost@cs.msu.su>
To: gdb@sources.redhat.com
Subject: Re: The 'x' command: size problem
Date: Tue, 06 Sep 2005 15:35:00 -0000 [thread overview]
Message-ID: <200509061935.12549.ghost@cs.msu.su> (raw)
In-Reply-To: <20050906152448.GA2444@nevyn.them.org>
On Tuesday 06 September 2005 19:24, Daniel Jacobowitz wrote:
> 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)
No, it's not very hard. But given anynchronious nature of communication with
gdb I'm trying to limit the number of queries to minimum, to minimize the
amount of data I have to keep.
<aside>
I might be wrong, but I feel it would be much better if gdb were a library
that I could link to. That would eliminate most anynchonious communication
and won't require to keep track which gdb reply corresponds to which
previously issued command and where the result of the command must be sent
inside the frontend.
</aside>
- Volodya
next prev parent reply other threads:[~2005-09-06 15:35 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
2005-09-06 15:35 ` Vladimir Prus [this message]
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=200509061935.12549.ghost@cs.msu.su \
--to=ghost@cs.msu.su \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).