[RFC] Support command "catch syscall" properly on different targets

Message ID 86zj7mgt3f.fsf@gmail.com
State New, archived
Headers

Commit Message

Yao Qi March 9, 2015, 2:09 p.m. UTC
  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.
  

Patch

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
 }