diff options
author | Pedro Alves <palves@redhat.com> | 2016-05-27 16:18:28 +0100 |
---|---|---|
committer | Pedro Alves <palves@redhat.com> | 2016-05-27 16:18:28 +0100 |
commit | 744608cc854a365661e93d307aadf22ab6e6bd7c (patch) | |
tree | 1383c929de09e8305c180543147b8cde761475a9 /opcodes | |
parent | e92bae62606702c1c07e095789ffed103e0e34c5 (diff) | |
download | gdb-744608cc854a365661e93d307aadf22ab6e6bd7c.zip gdb-744608cc854a365661e93d307aadf22ab6e6bd7c.tar.gz gdb-744608cc854a365661e93d307aadf22ab6e6bd7c.tar.bz2 |
Skip attach-many-short-lived-threads.exp on known-broken DejaGnu versions
If the testsuite is run with a DejaGnu version that predates the fix
from last year:
[PATCH] DejaGnu kills the wrong process due to PID-reuse races
http://lists.gnu.org/archive/html/dejagnu/2015-07/msg00005.html
... gdb.threads/attach-many-short-lived-threads.exp fails randomly,
often. Other tests randomly fail due to that issue too, but this one
is _much_ more exposed.
DejaGnu 1.6 was released meanwhile, which includes that DejaGnu fix,
and also some distros backported the fix too.
So skip the test when run with older/broken DejaGnus.
gdb/testsuite/ChangeLog:
2016-05-27 Pedro Alves <palves@redhat.com>
* gdb.threads/attach-many-short-lived-threads.exp (bad_dejagnu):
New procedure.
(top level): Call it, and bail out of DejaGnu is known to be bad.
Diffstat (limited to 'opcodes')
0 files changed, 0 insertions, 0 deletions