Fix gdb.threads/thread-specific-bp.exp race
authorPedro Alves <palves@redhat.com>
Wed, 4 Mar 2015 17:23:55 +0000 (17:23 +0000)
committerPedro Alves <palves@redhat.com>
Wed, 4 Mar 2015 17:23:55 +0000 (17:23 +0000)
commitbe9957b82fa4e09c53521335c2a7dddf6d208309
treec1fdb9e01b9e5e17c58b470159ab912ca1c4f173
parent79639e11323e209d3dfd1355abac3b83a87c6878
Fix gdb.threads/thread-specific-bp.exp race

Gary stumbled on this:

 (gdb) PASS: gdb.threads/thread-specific-bp.exp: all-stop: continue to end
 info threads
   Id   Target Id         Frame
 * 1    Thread 0x7ffff7fdb700 (LWP 13717) "thread-specific" end () at /home/gary/work/archer/startswith/src/gdb/testsuite/gdb.threads/thread-specific-bp.c:29
 (gdb) FAIL: gdb.threads/thread-specific-bp.exp: all-stop: thread start is gone
 info breakpoint

The problem is that "...archer/startswith/src..." has a "start" in it,
which matches the too-lax regex in the test.

Rather than tweaking the regex, we can just remove the whole "info
threads", like we removed similar ones in other files -- GDB nowadays
does this implicitly already, so things should work without it.  Thus
removing this even improves testing here a bit.

gdb/testsuite/ChangeLog:
2015-03-04  Pedro Alves  <palves@redhat.com>

* gdb.threads/thread-specific-bp.exp: Delete "info threads" test.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.threads/thread-specific-bp.exp
This page took 0.026091 seconds and 4 git commands to generate.