[PATCH] gdb: tests: mark async unsupported dynamically

[Mike Frysinger]

There are many targets which do not support asynchronous execution.
Rather than having the async tests mark them as FAIL, use UNSUPPORTED
as that better represents the state.
---
2015-06-19  Mike Frysinger  <vapier@gentoo.org>

	* gdb.base/async.exp (test_background): Call unsupported when async
	isn't supported.

 gdb/testsuite/gdb.base/async.exp | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/gdb/testsuite/gdb.base/async.exp b/gdb/testsuite/gdb.base/async.exp
index 2d3fb73..4b9168a 100644
--- a/gdb/testsuite/gdb.base/async.exp
+++ b/gdb/testsuite/gdb.base/async.exp
@@ -58,6 +58,9 @@ proc test_background {command before_prompt after_prompt {message ""}} {
 	-re "^$command\r\n${before_prompt}${gdb_prompt}${after_prompt}completed\.\r\n" {
 	    pass "$message"
 	}
+	-re "Asynchronous execution not supported on this target\.\r\n" {
+	    unsupported "$message"
+	}
 	-re "$gdb_prompt.*completed\.\r\n" {
 	    fail "$message"
 	}
-- 
2.2.0.rc0.207.ga3a616c