This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
[binutils-gdb] Set unknown_syscall differently on arm linux
- From: sergiodj+buildbot at sergiodj dot net
- To: gdb-testers at sourceware dot org
- Date: Sun, 17 Jul 2016 06:23:37 -0400
- Subject: [binutils-gdb] Set unknown_syscall differently on arm linux
- Authentication-results: sourceware.org; auth=none
*** TEST RESULTS FOR COMMIT 28244707d9e4f35cab1f9069cee1d44b38be095f ***
Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 28244707d9e4f35cab1f9069cee1d44b38be095f
Set unknown_syscall differently on arm linux
Currently, we use 123456789 as unknown or illegal syscall number, and
expect program return ENOSYS. Although 123456789 is an illegal syscall
number on arm linux, kernel sends SIGILL rather than returns -ENOSYS.
However, arm linux kernel returns -ENOSYS if syscall number is within
0xf0001..0xf07ff, so we can use 0xf07ff for unknown_syscall in test.
gdb/testsuite:
2016-06-29 Yao Qi <yao.qi@linaro.org>
* gdb.base/catch-syscall.c [__arm__]: Set unknown_syscall to
0x0f07ff.