From: Guillaume MENANT <guillaume.menant@geensys.com>
To: gdb@sourceware.org
Subject: Re: GDB commands
Date: Tue, 27 Nov 2007 10:46:00 -0000 [thread overview]
Message-ID: <13968586.post@talk.nabble.com> (raw)
In-Reply-To: <1196104670.2501.59.camel@localhost.localdomain>
Michael Snyder-3 wrote:
>
> On Mon, 2007-11-26 at 14:22 -0500, Daniel Jacobowitz wrote:
>> On Mon, Nov 26, 2007 at 11:01:47AM -0800, Michael Snyder wrote:
>> > 1) You need a way to read and write memory. There are
>> > several candidates, one being the original 'm' and 'M',
>> > another being the newer 'x' and 'X' (binary encoded).
>>
>> Just 'X', no 'x'; 'x' would be a logical addition but no one's been
>> round to it.
>>
>> All the rest of what Michael's written looks correct to me. You can
>> get by with very few packets... but if you want a useful debugging
>> stub, you may need more.
>>
>> I suspect '?' is mandatory.
>
> Ah, yes. ;-)
>
>
Thanks a lot for your answers. For now, I handle m, M, c, S, g, G, z, Z,
vFlashWrite, vFlashErase and vFlashDone.
--
View this message in context: http://www.nabble.com/GDB-commands-tf4843563.html#a13968586
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.
prev parent reply other threads:[~2007-11-27 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 13:44 Guillaume MENANT
2007-11-23 9:37 ` Guillaume MENANT
2007-11-23 11:05 ` Vladimir Prus
2007-11-23 12:27 ` Guillaume MENANT
2007-11-23 12:58 ` Vladimir Prus
2007-11-26 19:04 ` Michael Snyder
2007-11-26 19:21 ` Vladimir Prus
2007-11-26 19:14 ` Michael Snyder
2007-11-26 19:22 ` Daniel Jacobowitz
2007-11-26 19:30 ` Michael Snyder
2007-11-27 10:46 ` Guillaume MENANT [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=13968586.post@talk.nabble.com \
--to=guillaume.menant@geensys.com \
--cc=gdb@sourceware.org \
/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).