From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Carl Love <cel@us.ibm.com>, Simon Marchi <simark@simark.ca>,
John Baldwin <jhb@FreeBSD.org>,
gdb-patches@sourceware.org
Cc: Rogerio Alves <rogealve@br.ibm.com>
Subject: Re: [PATCH v2] gdb fix for catch-syscall.exp
Date: Fri, 10 Dec 2021 19:21:02 -0500 [thread overview]
Message-ID: <094fd87c-0e22-b874-a661-05759b20c696@polymtl.ca> (raw)
In-Reply-To: <5644a7484e2b2024166cd7a7d091d11052f96cc6.camel@us.ibm.com>
> gdb: Powerpc mark xfail in gdb.base/catch-syscall.exp
>
> Powerpc is not reporting the
>
> Catchpoint 1 (returned from syscall execve), ....
>
> as expected. The issue appears to be with the kernel not returning the
> expected result. This patch marks the test failure as an xfail.
>
> See gdb bugzilla https://sourceware.org/bugzilla/show_bug.cgi?id=28623
When we got rid of ChangeLogs, we agreed on the format:
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=28623
when referring to bugzilla entries, let's use that.
> ---
> gdb/testsuite/gdb.base/catch-syscall.exp | 38 ++++++++++++++++++++----
> 1 file changed, 32 insertions(+), 6 deletions(-)
>
> diff --git a/gdb/testsuite/gdb.base/catch-syscall.exp b/gdb/testsuite/gdb.base/catch-syscall.exp
> index cdd5e2aec47..76c5cfbc6d6 100644
> --- a/gdb/testsuite/gdb.base/catch-syscall.exp
> +++ b/gdb/testsuite/gdb.base/catch-syscall.exp
> @@ -127,7 +127,29 @@ proc check_return_from_syscall { syscall { pattern "" } } {
> }
>
> set thistest "syscall $syscall has returned"
> - gdb_test "continue" "Catchpoint $decimal \\(returned from syscall ${pattern}\\).*" $thistest
> + if { $pattern eq "execve" } {
> + gdb_test_multiple "continue" $thistest {
> + -re -wrap "Catchpoint $decimal \\(returned from syscall ${pattern}\\).*" {
> + pass $thistest
> + return 1
> + }
> + -re -wrap ".*Breakpoint $decimal, main .*" {
> + # On Powerpc kernel does not report the returned from syscall
kernel -> the kernel
returned -> return
> + # as expected by the test. GDB bugzilla 28623.
> + puts "CARLL test failed"
Leftover print.
Ok with those fixed.
Simon
prev parent reply other threads:[~2021-12-11 0:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 23:30 [PATCH] " Carl Love via Gdb-patches
2021-11-18 15:23 ` Tom Tromey
2021-11-18 18:10 ` Simon Marchi
2021-11-20 0:27 ` Carl Love via Gdb-patches
2021-11-22 1:07 ` Simon Marchi via Gdb-patches
2021-11-22 18:16 ` Carl Love via Gdb-patches
2021-11-22 17:01 ` John Baldwin
2021-11-23 20:34 ` Simon Marchi
2021-11-23 22:34 ` John Baldwin
2021-11-24 17:46 ` Carl Love via Gdb-patches
2021-11-24 17:51 ` John Baldwin
2021-11-24 1:15 ` Carl Love via Gdb-patches
2021-11-24 19:29 ` Simon Marchi
2021-11-29 16:46 ` Carl Love via Gdb-patches
2021-12-02 16:32 ` Ping " Carl Love via Gdb-patches
2021-12-10 18:36 ` Simon Marchi
2021-12-10 19:59 ` [PATCH v2] " Carl Love via Gdb-patches
2021-12-11 0:21 ` Simon Marchi via Gdb-patches [this message]
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=094fd87c-0e22-b874-a661-05759b20c696@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=cel@us.ibm.com \
--cc=jhb@FreeBSD.org \
--cc=rogealve@br.ibm.com \
--cc=simark@simark.ca \
--cc=simon.marchi@polymtl.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