No longer pull thread list explicitly
authorYao Qi <yao@codesourcery.com>
Wed, 8 Oct 2014 14:26:27 +0000 (22:26 +0800)
committerYao Qi <yao@codesourcery.com>
Sat, 11 Oct 2014 00:32:52 +0000 (08:32 +0800)
commit052ca3707367a7f1fae462a45c56e8e50fe3b98e
tree5402c3a7685e51bc071e63a169e62f03ac946b6a
parentad26045764197506da8e79adfb2c43798edeffff
No longer pull thread list explicitly

As the result of the patch below, GDB updates thread list when a stop is
presented to user.  The tests don't have to fetch thread list explicitly.

  [PATCH 3/3] Fix non-stop regressions caused by "breakpoints always-inserted off" changes
  https://sourceware.org/ml/gdb-patches/2014-09/msg00734.html

This patch is to remove the test code updating thread list.

Run these three tests many times on arm-linux-gnueabi and x86-linux.
No regressions.

gdb/testsuite:

2014-10-11  Yao Qi  <yao@codesourcery.com>

* gdb.threads/thread-find.exp: Don't execute command
"info threads".
* gdb.threads/attach-into-signal.exp (corefunc): Likewise.
* gdb.threads/linux-dp.exp: Don't check the condition
$threads_created equals to zero.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.threads/attach-into-signal.exp
gdb/testsuite/gdb.threads/linux-dp.exp
gdb/testsuite/gdb.threads/thread-find.exp