From: Pedro Alves <pedro@codesourcery.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Fix register cache invalidation
Date: Mon, 20 Jul 2009 13:58:00 -0000 [thread overview]
Message-ID: <200907201435.07453.pedro@codesourcery.com> (raw)
In-Reply-To: <200907141459.n6EExSxC004676@d12av02.megacenter.de.ibm.com>
On Tuesday 14 July 2009 15:59:28, Ulrich Weigand wrote:
> when testing the Cell/B.E. combined debugger patches I ran into a situation
> where registers_changed was not called soon enough.
>
> A while ago I proposed a patch to simplify register invalidation (as part of
> a infrun cleanup series):
> http://sourceware.org/ml/gdb-patches/2008-12/msg00120.html
> This cleanup actually fixes the combined debugger problem as well.
Curious. Are we sure we're not hidding some other bug then?
> At the time, Pedro pointed out that parts of that patch weren't safe in the
> non-stop case. The version below omits those parts, and only changes code
> to simplify calling registers_changed and resetting waiton_ptid.
> Tested on powerpc64-linux with no regressions.
> Any comments? I'd like to commit this in a couple of days.
I like it!
> > (fetch_inferior_event): Remove check for always-true condition.
>
> - /* We can only rely on wait_for_more being correct before handling
> - the event in all-stop, but previous_inferior_ptid isn't used in
> - non-stop. */
> - if (!ecs->wait_some_more)
> - /* We'll update this if & when we switch to a new thread. */
> - previous_inferior_ptid = inferior_ptid;
> + /* We'll update this if & when we switch to a new thread. */
> + previous_inferior_ptid = inferior_ptid;
This is actually a bug in the async/all-stop (you're not introducing
it, it's already there). We shouldn't be clobbering previous_inferior_ptid
on every internaly handled event. Just noting it --- don't worry about it.
--
Pedro Alves
next prev parent reply other threads:[~2009-07-20 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 20:22 Ulrich Weigand
2009-07-20 13:58 ` Pedro Alves [this message]
2009-07-20 15:14 ` Ulrich Weigand
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=200907201435.07453.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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