From: Richard Henderson <richard.henderson@linaro.org>
To: "Ilya Leoshkevich" <iii@linux.ibm.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [PATCH] tests/tcg: Fix the /proc/self/mem probing in the PROT_NONE gdbstub test
Date: Fri, 2 Feb 2024 14:20:28 +1000 [thread overview]
Message-ID: <f12bdb03-c855-4119-96b9-c9b6c1ba7232@linaro.org> (raw)
In-Reply-To: <20240131220245.235993-1-iii@linux.ibm.com>
On 2/1/24 08:02, Ilya Leoshkevich wrote:
> The `if not probe_proc_self_mem` check never passes, because
> probe_proc_self_mem is a function object, which is a truthy value.
> Add parentheses in order to perform a function call.
>
> Fixes: dc84d50a7f9b ("tests/tcg: Add the PROT_NONE gdbstub test")
> Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
> ---
> tests/tcg/multiarch/gdbstub/prot-none.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/tcg/multiarch/gdbstub/prot-none.py b/tests/tcg/multiarch/gdbstub/prot-none.py
> index e829d3ebc5f..7e264589cb8 100644
> --- a/tests/tcg/multiarch/gdbstub/prot-none.py
> +++ b/tests/tcg/multiarch/gdbstub/prot-none.py
> @@ -20,7 +20,7 @@ def probe_proc_self_mem():
>
> def run_test():
> """Run through the tests one by one"""
> - if not probe_proc_self_mem:
> + if not probe_proc_self_mem():
> print("SKIP: /proc/self/mem is not usable")
> exit(0)
> gdb.Breakpoint("break_here")
Ack. Queued to tcg-next.
r~
next prev parent reply other threads:[~2024-02-02 4:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 22:02 [PATCH] tests/tcg: Fix the /proc/self/mem probing in the PROT_NONE gdbstub test Ilya Leoshkevich
2024-02-02 4:20 ` Richard Henderson [this message]
2024-02-03 20:48 ` Michael Tokarev
2024-02-05 9:58 ` Ilya Leoshkevich
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=f12bdb03-c855-4119-96b9-c9b6c1ba7232@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=iii@linux.ibm.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).