From: "Jon Beniston" <jon@beniston.com>
To: "'Yao Qi'" <yao@codesourcery.com>
Cc: <gdb@sourceware.org>
Subject: RE: Memory-mapped peripheral registers, remote protocol and memory maps
Date: Thu, 29 Nov 2012 16:32:00 -0000 [thread overview]
Message-ID: <009401cdce4f$03913a80$0ab3af80$@beniston.com> (raw)
In-Reply-To: <50B727B8.7040103@codesourcery.com>
> The following command 'p' will only generate 'm' packet with the right size.
>
> (gdb) p *(unsigned int *) 0x8048608
> Sending packet: $m8048608,4#3f...Packet received: 5589e583
>
>
> (gdb) p *(char *) 0x8048608
> Sending packet: $m8048608,1#3c...Packet received: 55
>
> I admit they are tricky.
Yes, this is fine from the command line, but ideally I would like something that works when GDB is being driven by a GUI such as Eclipse, which may not necessarily know the correct size to use. It does work in some cases, but not all (i.e. when dumping memory).
Thanks for the pointer, I'll see if I can find the patches you mention.
Cheers,
Jon
next prev parent reply other threads:[~2012-11-29 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 19:24 Jon Beniston
2012-11-29 9:16 ` Yao Qi
2012-11-29 11:23 ` Jon Beniston
2012-11-29 15:51 ` Yao Qi
2012-11-29 16:32 ` Jon Beniston [this message]
2012-11-29 17:23 ` Paul_Koning
2012-11-29 17:57 ` Jon Beniston
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='009401cdce4f$03913a80$0ab3af80$@beniston.com' \
--to=jon@beniston.com \
--cc=gdb@sourceware.org \
--cc=yao@codesourcery.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).