public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Lancelot SIX <lsix@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb_spawn_attach_cmdline: use unsupported instead of untested
Date: Thu, 21 Apr 2022 13:42:07 +0000 (GMT)	[thread overview]
Message-ID: <20220421134207.70E55385741C@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=78088b89602ad5c2b68142d6a56481fb792725aa

commit 78088b89602ad5c2b68142d6a56481fb792725aa
Author: Lancelot SIX <lancelot.six@amd.com>
Date:   Thu Apr 21 09:28:21 2022 +0100

    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:
---
 gdb/testsuite/lib/gdb.exp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 0c00d599ca5..47cb2b23676 100644
--- 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\\." {


                 reply	other threads:[~2022-04-21 13:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220421134207.70E55385741C@sourceware.org \
    --to=lsix@sourceware.org \
    --cc=gdb-cvs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).