gdb_spawn_attach_cmdline: use unsupported instead of untested

In a previous commit (b750766ac96: gdb/testsuite: Introduce and use
gdb_spawn_attach_cmdline), if gdb_spawn_attach_cmdline cannot have GDB
attach to the process because of ptrace restrictions (operation not
permitted), the proc issues UNTESTED.  This should really be
UNSUPPORTED, as it is done in gdb_attach.

This patch fixes this oversight.

Change-Id: Ib87e33b9230f3fa7a85e06220ef4c63814b71f7d

diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 0c00d599ca52b73845639c4dce6ce16d1b49e5d7..47cb2b2367665d1a1018cbd94004cab0af8549ae 100644 (file)
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -5205,7 +5205,7 @@ proc_with_prefix gdb_spawn_attach_cmdline { testpid } {
 
     gdb_test_multiple "" "$test" {
        -re -wrap "ptrace: Operation not permitted\\." {
-           untested "$gdb_test_name (operation not permitted)"
+           unsupported "$gdb_test_name (operation not permitted)"
            return 0
        }
        -re -wrap "ptrace: No such process\\." {