From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH/python] notify memory changed.
Date: Fri, 22 Jun 2012 14:35:00 -0000 [thread overview]
Message-ID: <87395njtyr.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1375760.Ghu1pfDITS@qiyao.dyndns.org> (Yao Qi's message of "Thu, 21 Jun 2012 09:53:49 +0800")
>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:
Yao> 2012-06-21 Yao Qi <yao@codesourcery.com>
Yao> * corefile.c (write_memory_with_notification): New.
Yao> Include "observer.h".
Yao> * gdbcore.h: Declare write_memory_with_notification.
Yao> * ada-lang.c (ada_value_assign): Replace 'write_memory' and
Yao> 'observer_notify_memory_changed' with 'write_memory_with_notification'.
Yao> * valops.c (value_assign): Likewise.
Yao> * python/py-inferior.c (infpy_write_memory): Call
Yao> 'write_memory_with_notification'.
Ok.
Tom
prev parent reply other threads:[~2012-06-22 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 3:16 Yao Qi
2012-06-19 15:14 ` Joel Brobecker
2012-06-20 3:46 ` Yao Qi
2012-06-20 14:52 ` Joel Brobecker
2012-06-21 1:54 ` Yao Qi
2012-06-21 8:52 ` Abid, Hafiz
[not found] ` <2883062.LPF6KAsNoT@qiyao.dyndns.org>
2012-06-22 14:36 ` Tom Tromey
2012-06-22 14:35 ` Tom Tromey [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=87395njtyr.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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