Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [Patch 1/2] Fix aftermath of 'infrun.c support for MIPS hardware   watchpoints.'
Date: Mon, 20 Apr 2009 21:15:00 -0000	[thread overview]
Message-ID: <49ECE5CB.6000708@caviumnetworks.com> (raw)
In-Reply-To: <200904202007.37943.pedro@codesourcery.com>

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

Pedro Alves wrote:
> 
> In the mean time, your patch is OK.  I'd just move the
> registers_changed call to *after* target_resume, because the 
> target_resume implementation could trigger a register cache
> refetch, thus reintroducing the problem (e.g., it doesn't happen
> on mips *today*, but see e.g., i386-linux-nat.c:i386_linux_resume).  I'd
> put it right after the prepare_to_wait call.
> 
>> 2009-04-20  David Daney  <ddaney@caviumnetworks.com>
>>
>>         * infrun.c (handle_inferior_event): Move registers_changed call down.
>>

This is the version I committed.

Thanks for taking the time to review these.

2009-04-20  David Daney  <ddaney@caviumnetworks.com>

         * infrun.c (handle_inferior_event): Move registers_changed call 
down.

[-- Attachment #2: infrun.patch --]
[-- Type: text/plain, Size: 719 bytes --]

Index: infrun.c
===================================================================
RCS file: /cvs/src/src/gdb/infrun.c,v
retrieving revision 1.368
diff -u -p -r1.368 infrun.c
--- infrun.c	14 Apr 2009 00:59:47 -0000	1.368
+++ infrun.c	20 Apr 2009 21:06:10 -0000
@@ -2842,10 +2842,10 @@ targets should add new threads to the th
 
       if (!HAVE_STEPPABLE_WATCHPOINT)
 	remove_breakpoints ();
-      registers_changed ();
 	/* Single step */
       hw_step = maybe_software_singlestep (current_gdbarch, read_pc ());
       target_resume (ecs->ptid, hw_step, TARGET_SIGNAL_0);
+      registers_changed ();
       waiton_ptid = ecs->ptid;
       if (HAVE_STEPPABLE_WATCHPOINT)
 	infwait_state = infwait_step_watch_state;

  reply	other threads:[~2009-04-20 21:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06  7:27 [Patch 2/2] MIPS hardware watchpoint support David Daney
2009-04-06 20:27 ` Eli Zaretskii
2009-04-11 17:16 ` Pedro Alves
2009-04-16 17:08   ` David Daney
2009-04-17 13:43     ` Pedro Alves
2009-04-20 18:31       ` [Patch 1/2] Fix aftermath of 'infrun.c support for MIPS hardware watchpoints.' David Daney
2009-04-20 19:07         ` Pedro Alves
2009-04-20 21:15           ` David Daney [this message]
2009-04-20 18:40       ` [Patch 2/2] MIPS hardware watchpoint support David Daney
2009-04-20 19:12         ` Pedro Alves

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=49ECE5CB.6000708@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@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