aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.threads
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2016-05-27 16:18:28 +0100
committerPedro Alves <palves@redhat.com>2016-05-27 16:18:28 +0100
commit744608cc854a365661e93d307aadf22ab6e6bd7c (patch)
tree1383c929de09e8305c180543147b8cde761475a9 /gdb/testsuite/gdb.threads
parente92bae62606702c1c07e095789ffed103e0e34c5 (diff)
downloadgdb-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 'gdb/testsuite/gdb.threads')
-rw-r--r--gdb/testsuite/gdb.threads/attach-many-short-lived-threads.exp34
1 files changed, 34 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.threads/attach-many-short-lived-threads.exp b/gdb/testsuite/gdb.threads/attach-many-short-lived-threads.exp
index ccb5e9b..3bac28d 100644
--- a/gdb/testsuite/gdb.threads/attach-many-short-lived-threads.exp
+++ b/gdb/testsuite/gdb.threads/attach-many-short-lived-threads.exp
@@ -21,6 +21,40 @@
# end up leaving stale state behind that confuse the following
# attach).
+# Return true if the running version of DejaGnu is known to not be
+# able to run this test.
+proc bad_dejagnu {} {
+ global frame_version
+
+ verbose -log "DejaGnu version: $frame_version"
+ verbose -log "Expect version: [exp_version]"
+ verbose -log "Tcl version: [info tclversion]"
+
+ set dj_ver [split $frame_version .]
+ set dj_ver_major [lindex $dj_ver 0]
+ set dj_ver_minor [lindex $dj_ver 1]
+
+ # DejaGnu versions prior to 1.6 manage to kill the wrong process
+ # due to PID-reuse races. Since this test spawns many threads, it
+ # widens the race window a whole lot, enough that the inferior is
+ # often killed, and thus the test randomly fails. See:
+ # http://lists.gnu.org/archive/html/dejagnu/2015-07/msg00005.html
+ # The fix added a close_wait_program procedure. If that procedure
+ # is defined, and DejaGnu is older than 1.6, assume that means the
+ # fix was backported.
+ if {$dj_ver_major == 1
+ && ($dj_ver_minor < 6 && [info procs close_wait_program] == "")} {
+ return 1
+ }
+
+ return 0
+}
+
+if {[bad_dejagnu]} {
+ unsupported "broken DejaGnu"
+ return 0
+}
+
if {![can_spawn_for_attach]} {
return 0
}