From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Lancelot SIX <lancelot.six@amd.com>, gdb-patches@sourceware.org
Cc: lsix@lancelotsix.com
Subject: Re: [PATCH] gdb_spawn_attach_cmdline: use unsupported instead of untested
Date: Thu, 21 Apr 2022 09:40:16 -0400 [thread overview]
Message-ID: <ec20cc39-a760-340b-dfd3-cc848c013577@simark.ca> (raw)
In-Reply-To: <20220421083655.48459-1-lancelot.six@amd.com>
On 2022-04-21 04:36, Lancelot SIX via Gdb-patches wrote:
> 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
> ---
> 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\\." {
>
> base-commit: 333cd559bae5a6be60832c020da479ae23fd2664
> --
> 2.25.1
>
This makes sense, please push, thanks.
Simon
next prev parent reply other threads:[~2022-04-21 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 8:36 Lancelot SIX via Gdb-patches
2022-04-21 13:40 ` Simon Marchi via Gdb-patches [this message]
2022-04-21 13:42 ` Lancelot SIX via Gdb-patches
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=ec20cc39-a760-340b-dfd3-cc848c013577@simark.ca \
--to=gdb-patches@sourceware.org \
--cc=lancelot.six@amd.com \
--cc=lsix@lancelotsix.com \
--cc=simark@simark.ca \
/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