This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v3][PR remote/16896] Invalidate a register in cache when a remote target failed to write it.
- From: Pedro Alves <palves at redhat dot com>
- To: Pierre Langlois <pierre dot langlois at embecosm dot com>, gdb-patches at sourceware dot org
- Date: Thu, 12 Jun 2014 19:17:44 +0100
- Subject: Re: [PATCH v3][PR remote/16896] Invalidate a register in cache when a remote target failed to write it.
- Authentication-results: sourceware.org; auth=none
- References: <1402594537-8033-1-git-send-email-pierre dot langlois at embecosm dot com>
Excellent, thanks.
On 06/12/2014 06:35 PM, Pierre Langlois wrote:
" I was wondering how to go about adding a test for this in
> the GDB testsuite. Could we include faulty dummy servers to test each packets?"
These two sentences shouldn't really be in the commit log.
But to answer, if we can make that work, I don't see why not.
I don't think that's a trivial effort though.
> + chain_before_invalidate_register =
> + make_cleanup_regcache_invalidate (regcache, regnum);
I missed this before, but '=' goes on the next line, like:
chain_before_invalidate_register
= make_cleanup_regcache_invalidate (regcache, regnum);
OK with these changes.
Thanks!
--
Pedro Alves