From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: "Ulrich Weigand" <uweigand@de.ibm.com>
Subject: Re: Fixes for a couple of infrun bugs (thread hop, revert to step thread).
Date: Mon, 16 Aug 2010 18:53:00 -0000 [thread overview]
Message-ID: <201008161952.53200.pedro@codesourcery.com> (raw)
In-Reply-To: <201008161840.o7GIel4W024223@d12av02.megacenter.de.ibm.com>
On Monday 16 August 2010 19:40:47, Ulrich Weigand wrote:
> Pedro Alves wrote:
>
> > Replacing the "next" by a "continue" should work. I've looked over the
> > original description of the problem this is covering, and, that
> > would still exercise the problem (which is gdb trying to step
> > the other (main) thread with inferior_ptid still pointing at
> > the thread that was being "next"ed, and in the process failing
> > to remove breakpoints from memory because inferior_ptid pointed
> > at an inferior thread.
>
> But isn't the code your patch changes under an if that's only true
> if another thread is currently being stepped or nexted? If we just
> do "continue" here, that's no longer the case, and the code wouldn't
> be exercised at all ...
That's also exercised by the other test my original patch added,
IIRC (gdb.thread/thread-execl.exp). There were two bugs fixed by
that patch. The specific bug the threxit-hop-specific.exp test is
covering is the "failing to remove breakpoints" one.
--
Pedro Alves
next prev parent reply other threads:[~2010-08-16 18:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 22:00 Pedro Alves
2009-05-28 11:12 ` Ulrich Weigand
2009-05-28 17:20 ` Pedro Alves
2009-06-09 19:58 ` Joel Brobecker
2009-06-10 16:20 ` Pedro Alves
2009-06-10 16:37 ` Joel Brobecker
2010-08-16 17:38 ` Ulrich Weigand
2010-08-16 18:30 ` Pedro Alves
2010-08-16 18:32 ` Pedro Alves
2010-08-16 18:41 ` Ulrich Weigand
2010-08-16 18:53 ` Pedro Alves [this message]
2010-08-16 19:01 ` Ulrich Weigand
2010-09-08 18:18 ` [commit] " 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=201008161952.53200.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