Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/tests
History
kamil 05ffc73c35 Add new ptrace(2) API: PT_SETSTEP & PT_CLEARSTEP 
These operations allow to mark thread as a single-stepping one.

This allows to i.a.:
 - single step and emit a signal (PT_SETSTEP & PT_CONTINUE)
 - single step and trace syscall entry and exit (PT_SETSTEP & PT_SYSCALL)

The former is useful for debuggers like GDB or LLDB. The latter can be used
to singlestep a usermode kernel. These examples don't limit use-cases of
this interface.

Define PT_*STEP only for platforms defining PT_STEP.

Add new ATF tests setstep[1234].

These ptrace(2) operations first appeared in FreeBSD.

Sponsored by <The NetBSD Foundation>
 		2017-04-08 00:25:49 +00:00
..
bin PR bin/52090 - the $* tests are no longer expected to fail. 2017-03-20 11:48:41 +00:00
crypto periphereal updates and generated files for the new openssl. 2016-10-14 16:09:43 +00:00
dev Do not assume an all-zeroes disk label will read back as a disk with 2017-03-15 10:53:15 +00:00
fs Add failing test cases for PRs kern/2423, kern/3645, kern/4597 2017-03-26 18:26:05 +00:00
games Do this more cleanly - put the do-we-have-crypto check inside the actual 2016-06-27 05:29:32 +00:00
include Don't play with "../.." in includes for h_macros.h; deal with it centrally. 2017-01-13 21:30:39 +00:00
ipf Remove the "expected failure" from test n12, and change it not to use 2015-12-26 08:01:58 +00:00
kernel Remove tests/kernel/t_ptrace* from the tree 2017-04-03 05:06:28 +00:00
lib Add new ptrace(2) API: PT_SETSTEP & PT_CLEARSTEP 2017-04-08 00:25:49 +00:00
libexec Don't play with "../.." in includes for h_macros.h; deal with it centrally. 2017-01-13 21:30:39 +00:00
modules Don't play with "../.." in includes for h_macros.h; deal with it centrally. 2017-01-13 21:30:39 +00:00
net Add test cases for ping options 2017-03-31 06:41:40 +00:00
rump Don't play with "../.." in includes for h_macros.h; deal with it centrally. 2017-01-13 21:30:39 +00:00
sbin Skip the "migrate" test on architectures not natively using MBR, it 2017-03-22 19:13:40 +00:00
share When no gcc but clang can be found, fallback to the latter instead of 2016-03-12 08:55:54 +00:00
sys convention about function names for predicate checking: 2016-12-22 08:15:20 +00:00
usr.bin new test 2017-03-06 23:07:42 +00:00
usr.sbin PR/51876: Ngie Cooper: kyua 0.11 $TMPDIR fixes 2017-01-14 20:45:16 +00:00
Makefile
…
Makefile.inc better name 2017-01-14 01:33:32 +00:00
README
…
h_macros.h provide an RL variant that prints an extra argument 2016-08-20 15:49:08 +00:00

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.