Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: pedro@codesourcery.com (Pedro Alves)
Cc: gdb-patches@sourceware.org
Subject: [commit] Re: Fixes for a couple of infrun bugs (thread hop, revert to step thread).
Date: Wed, 08 Sep 2010 18:18:00 -0000	[thread overview]
Message-ID: <201009081751.o88Hpufw019331@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <201008161952.53200.pedro@codesourcery.com> from "Pedro Alves" at Aug 16, 2010 07:52:52 PM

Pedro Alves wrote:
> 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.

OK, I've now committed the following patch.

Tested on armv7l-linux-gnueabi and i686-linux.

Thanks,
Ulrich


ChangeLog:

	* gdb.threads/threxit-hop-specific.exp: Use "continue" instead
	of "next" to proceed over pthread_exit call.

Index: gdb/testsuite/gdb.threads/threxit-hop-specific.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.threads/threxit-hop-specific.exp,v
retrieving revision 1.2
diff -u -p -r1.2 threxit-hop-specific.exp
--- gdb/testsuite/gdb.threads/threxit-hop-specific.exp	1 Jan 2010 07:32:06 -0000	1.2
+++ gdb/testsuite/gdb.threads/threxit-hop-specific.exp	16 Aug 2010 19:05:38 -0000
@@ -52,7 +52,7 @@ gdb_test "break $bpthrline thread 2" \
 set bpexitline [gdb_get_line_number "set exit breakpoint here"]
 gdb_breakpoint "$bpexitline"
 
-gdb_test "next" \
+gdb_test "continue" \
     ".*set exit breakpoint here.*" \
     "get past the thread specific breakpoint"
 


-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


      parent reply	other threads:[~2010-09-08 17:52 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
2010-08-16 19:01         ` Ulrich Weigand
2010-09-08 18:18         ` Ulrich Weigand [this message]

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=201009081751.o88Hpufw019331@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.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