diff options
| author | Stefan Liebler <stli@linux.vnet.ibm.com> | 2017-07-11 10:37:03 +0200 |
|---|---|---|
| committer | Stefan Liebler <stli@linux.vnet.ibm.com> | 2017-07-11 10:38:44 +0200 |
| commit | 2c804457879c2dd76823d1b47f1a1eba5073727c (patch) | |
| tree | 97a2efc167a6bdaa1a7f370102c08d9725a92fc8 /misc/mkostemps64.c | |
| parent | 38eea35ca7aa8909e2225da15dd5e1f27650ec71 (diff) | |
| download | glibc-2c804457879c2dd76823d1b47f1a1eba5073727c.tar glibc-2c804457879c2dd76823d1b47f1a1eba5073727c.tar.gz glibc-2c804457879c2dd76823d1b47f1a1eba5073727c.tar.bz2 glibc-2c804457879c2dd76823d1b47f1a1eba5073727c.zip | |
S390: Fix tst-ptrace-singleblock if kernel does not support PTRACE_SINGLEBLOCK.
The request PTRACE_SINGLEBLOCK was introduced in Linux 3.15. Thus the ptrace call
will fail on older kernels.
Thus the test is now testing PTRACE_SINGLEBLOCK with data argument pointing to a
buffer on stack which is assumed to fail. If the request would be interpreted as
PTRACE_GETREGS, then the ptrace call will not fail and the regs are written to buf.
If we run with a kernel with support for PTRACE_SINGLEBLOCK a ptrace call with
data=NULL, returns zero with no error. If we run with a kernel without support for
PTRACE_SINGLEBLOCK a ptrace call with data=NULL reports an error.
In the latter case, the test is just continuing with PTRACE_CONT.
ChangeLog:
* sysdeps/unix/sysv/linux/s390/tst-ptrace-singleblock.c:
Support running on kernels without PTRACE_SINGLEBLOCK.
Diffstat (limited to 'misc/mkostemps64.c')
0 files changed, 0 insertions, 0 deletions