From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [RFA/commit] undefined regcache_set_valid_p in remote-mips.c
Date: Mon, 16 Mar 2009 20:07:00 -0000 [thread overview]
Message-ID: <20090316195430.GH9576@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
remote-mips.c no longer builds because of this call to regcache_set_valid_p.
I couldn't find any trace of that routine in our ChangeLogs and I'm right
in the middle of a rather large change in my git directory, so I didn't
bother investigate more about this routine.
I think that the routine that we want, right now, is called
regcache_invalidate.
2009-03-16 Joel Brobecker <brobecker@adacore.com>
* remote-mips.c (mips_load): Replace call to regcache_set_valid_p,
which is undefined, by call to regcache_invalidate, which should
do what the original author wanted to do.
Does this look plausible to anyone else? I'd just like a second pair
of eyes before I commit.
Thank you!
--
Joel
[-- Attachment #2: remote-mips.c.diff --]
[-- Type: text/x-diff, Size: 825 bytes --]
Index: remote-mips.c
===================================================================
RCS file: /cvs/src/src/gdb/remote-mips.c,v
retrieving revision 1.97
diff -u -p -r1.97 remote-mips.c
--- remote-mips.c 16 Mar 2009 19:38:32 -0000 1.97
+++ remote-mips.c 16 Mar 2009 19:50:15 -0000
@@ -3276,9 +3276,9 @@ mips_load (char *file, int from_tty)
to a different value than GDB thinks it has. The following ensures
that the write_pc() WILL update the PC value: */
struct regcache *regcache = get_current_regcache ();
- regcache_set_valid_p (regcache,
- gdbarch_pc_regnum (get_regcache_arch (regcache)),
- 0);
+
+ regcache_invalidate (regcache,
+ gdbarch_pc_regnum (get_regcache_arch (regcache)));
}
if (exec_bfd)
write_pc (bfd_get_start_address (exec_bfd));
next reply other threads:[~2009-03-16 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 20:07 Joel Brobecker [this message]
2009-03-16 20:09 ` Daniel Jacobowitz
2009-03-16 20:20 ` Pedro Alves
2009-03-16 21:19 ` Joel Brobecker
2009-03-16 21:44 ` Pedro Alves
2009-03-16 22:52 ` Joel Brobecker
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=20090316195430.GH9576@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@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