aboutsummaryrefslogtreecommitdiff
path: root/intl
diff options
context:
space:
mode:
authorYao Qi <yao.qi@linaro.org>2016-06-28 12:02:35 +0100
committerYao Qi <yao.qi@linaro.org>2016-06-28 12:03:28 +0100
commita31d2f068fa1384c505b540ea595d2d97813ba5f (patch)
treeffd9ad9973ea5a03e93a318e79dc0b2687cb6ffd /intl
parent7160c10d6530b79ea45d435933b07765f610f54d (diff)
downloadgdb-a31d2f068fa1384c505b540ea595d2d97813ba5f.zip
gdb-a31d2f068fa1384c505b540ea595d2d97813ba5f.tar.gz
gdb-a31d2f068fa1384c505b540ea595d2d97813ba5f.tar.bz2
Probe catch syscall support
In 82075af2c14b1f8a54fa5796fb63f7ef23f98d9d (Implement 'catch syscall' for gdbserver), only x86 is supported, but the test can still be run on other linux targets, like aarch64 and ppc, with native-gdbserver. This causes many new fails. This patch removes the check on isnative and on target triplets. Instead, we can insert catch point, and resume the program to see whether catch syscall is supported or not. gdb/testsuite: 2016-06-28 Yao Qi <yao.qi@linaro.org> * gdb.base/catch-syscall.exp: Remove check on isnative and target triplets. Start gdb, execute catch syscall, and continue. Check gdb's output to determine catch syscall is supported.
Diffstat (limited to 'intl')
0 files changed, 0 insertions, 0 deletions