From: "André Pönitz" <apoenitz@trolltech.com>
To: gdb@sourceware.org
Subject: Re: Manipulating memory
Date: Thu, 07 Aug 2008 09:12:00 -0000 [thread overview]
Message-ID: <200808071114.58561.apoenitz@trolltech.com> (raw)
In-Reply-To: <d557d0790808070042w6783e68bv8de47a62a41a4891@mail.gmail.com>
On Thursday 07 August 2008 09:42:23 Eran Ifrah wrote:
> On Thu, Aug 7, 2008 at 10:15 AM, Nick Roberts <nickrob@snap.net.nz> wrote:
> > > > GDB has an undocumented MI command called -data-write-memory. I've not
> > > > used it though, and don't know if it works or does what you want.
> > > >
> > >
> > > Thanks ! this is exactly what I was looking for: the sibling function
> > > of -data-read-memory.
> > >
> > > Any ideas why this command is undocumented?
> >
> > Not really. If it works for you, perhaps you could documentation.
> I was not referring to the actual documentation, but maybe there is a
> reason for that? unsupported?
>
> But, I will document it once I will explore all its options.
As side note: And maybe documentation for non-implemented
features could be removed.
For the original problem: looks like
set {char[100]} buffer_in_debuggee = { 's','o','m','e',' ','d','a','t','a',0 }
works.
André
next prev parent reply other threads:[~2008-08-07 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 19:04 Eran Ifrah
2008-08-05 19:12 ` Joel Brobecker
2008-08-05 19:37 ` Sheng-Liang Song
2008-08-06 6:36 ` André Pönitz
2008-08-06 8:15 ` Nick Roberts
[not found] ` <d557d0790808060122x67edceb8h559caa8d2670316b@mail.gmail.com>
[not found] ` <18586.41219.18256.847372@kahikatea.snap.net.nz>
2008-08-07 7:43 ` Eran Ifrah
2008-08-07 9:12 ` André Pönitz [this message]
2008-08-07 18:15 ` Eli Zaretskii
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=200808071114.58561.apoenitz@trolltech.com \
--to=apoenitz@trolltech.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