From: Yao Qi <qiyaoltc@gmail.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Pedro Alves <palves@redhat.com>, Yao Qi <qiyaoltc@gmail.com>,
gdb-patches@sourceware.org
Subject: Re: [RFC] Support command "catch syscall" properly on different targets
Date: Mon, 09 Mar 2015 14:10:00 -0000 [thread overview]
Message-ID: <86zj7mgt3f.fsf@gmail.com> (raw)
In-Reply-To: <87bnkaklbe.fsf@redhat.com> (Sergio Durigan Junior's message of "Tue, 03 Mar 2015 13:06:13 -0500")
Sergio Durigan Junior <sergiodj@redhat.com> writes:
> I remember seeing TARGET_WAITKIND_SYSCALL_{ENTRY,RETURN} when
> implementing "catch syscall", and I even remember making a decision to
> use them instead of creating other TARGET_WAITKIND's. However, the
> "catch syscall" itself doesn't work on HP-UX.
>
> Anyway, I just raised this point because we shouldn't "return 1" when
> asked if inf-ttrace.c supports "catch syscall".
So let's skip catch-syscall.exp on HP-UX target.
--
Yao (齐尧)
From: Yao Qi <yao.qi@linaro.org>
Date: Mon, 9 Mar 2015 13:59:38 +0000
Subject: [PATCH] Skip catch-syscall.exp on HP-UX target
"catch syscall" doesn't work on HP-UX.
gdb/testsuite:
2015-03-09 Yao Qi <yao.qi@linaro.org>
* gdb.base/catch-syscall.exp: Skip it on HP-UX target.
diff --git a/gdb/testsuite/gdb.base/catch-syscall.exp b/gdb/testsuite/gdb.base/catch-syscall.exp
index 498ae36..b8cc169 100644
--- a/gdb/testsuite/gdb.base/catch-syscall.exp
+++ b/gdb/testsuite/gdb.base/catch-syscall.exp
@@ -29,7 +29,7 @@ if { ![istarget "x86_64-*-linux*"] && ![istarget "i\[34567\]86-*-linux*"]
&& ![istarget "powerpc-*-linux*"] && ![istarget "powerpc64-*-linux*"]
&& ![istarget "sparc-*-linux*"] && ![istarget "sparc64-*-linux*"]
&& ![istarget "mips*-linux*"] && ![istarget "arm*-linux*"]
- && ![istarget "s390*-linux*"] && ![istarget "hppa*-hp-hpux*"] } {
+ && ![istarget "s390*-linux*"] } {
continue
}
prev parent reply other threads:[~2015-03-09 14:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 14:23 Yao Qi
2015-02-27 18:49 ` Doug Evans
2015-03-03 11:56 ` Yao Qi
2015-03-03 12:14 ` Pedro Alves
2015-02-27 18:50 ` Pedro Alves
2015-03-03 12:06 ` Yao Qi
2015-03-03 12:38 ` Pedro Alves
2015-02-27 21:04 ` Sergio Durigan Junior
2015-03-03 12:11 ` Yao Qi
2015-03-03 12:29 ` Pedro Alves
2015-03-03 18:06 ` Sergio Durigan Junior
2015-03-03 18:18 ` Pedro Alves
2015-03-06 16:36 ` Yao Qi
2015-03-06 22:04 ` Sergio Durigan Junior
2015-03-09 14:29 ` Yao Qi
2015-03-10 4:53 ` Sergio Durigan Junior
2015-03-09 14:10 ` Yao Qi [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=86zj7mgt3f.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sergiodj@redhat.com \
/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