9e277af53b
These tests are for the proposed PT_[GS]ET_SIGINFO interface for ptrace(2), accessors for signal information that caused tracee to be interrupted. siginfo1: Verify basic PT_GET_SIGINFO call for SIGTRAP from tracee siginfo2: Verify basic PT_GET_SIGINFO and PT_SET_SIGINFO calls without modification of SIGINT from tracee siginfo3: Verify basic PT_GET_SIGINFO and PT_SET_SIGINFO calls with setting signal to new value New tests are protected with #ifded and currently disabled in the HEAD branch. They will be automatically enabled once the final implementation will land the sources. Sponsored by <The NetBSD Foundation> |
||
---|---|---|
.. | ||
bin | ||
crypto | ||
dev | ||
fs | ||
games | ||
include | ||
ipf | ||
kernel | ||
lib | ||
libexec | ||
modules | ||
net | ||
rump | ||
sbin | ||
share | ||
sys | ||
usr.bin | ||
usr.sbin | ||
Makefile | ||
Makefile.inc | ||
README | ||
h_macros.h |
README
$NetBSD: README,v 1.4 2012/05/18 15:36:21 jruoho Exp $ When adding new tests, please try to follow the following conventions. 1. For library routines, including system calls, the directory structure of the tests should follow the directory structure of the real source tree. For instance, interfaces available via the C library should follow: src/lib/libc/gen -> src/tests/lib/libc/gen src/lib/libc/sys -> src/tests/lib/libc/sys ... 2. Equivalently, all tests for userland utilities should try to follow their location in the source tree. If this can not be satisfied, the tests for a utility should be located under the directory to which the utility is installed. Thus, a test for env(1) should go to src/tests/usr.bin/env. Likewise, a test for tcpdump(8) should be in src/tests/usr.sbin/tcpdump, even though the source code for the program is located under src/external. 3. Otherwise use your own discretion.