NetBSD

History

kamil aaef92583a Extend ATF tests in t_trapsignal.sh to verify software breakpoint traps There are at least four types of SIGTRAP events: - software/hardware single step (trace trap) - software breakpoint - hardware breakpoint/watchpoint - kernel event (exec, fork, vfork, vfork-done, lwp-create, lwp-exit) A program can execute software breakpoint without the context of being traced and this is a regular crash signal emitting SIGTRAP (TRAP_BRKPT). Rename original trap_* tests (trap_simple, trap_handle, trap_mask, trap_handle_recurse and trap_ignore) to segv_* tests and restrict them for SIGSEGV. Add new tests: trap_* testing the same scenarios as segv_ ones, however verifying the software breakpoint trap (SIGTRAP). Keep the original name of h_segv.c, and extend it for software breakpoint events. The purpose of these tests is to verify SIGTRAP kernel paths without the ptrace(2) context. All tests pass. Sponsored by <The NetBSD Foundation>		2018-05-22 04:32:56 +00:00
..
bin	Add a test case for PR bin/53201	2018-04-21 21:28:35 +00:00
crypto	PR lib/53044: remove tests not provided by OpenSSL 1.1.x	2018-02-22 14:24:03 +00:00
dev	implement 32-bit compat support for raidframe.	2018-01-18 00:32:48 +00:00
fs	Use sysctl -n rather than parse the output.	2018-01-17 00:23:17 +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	Update recently-added test to adapt to new signature of LIST_MOVE()	2017-10-02 05:14:29 +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	Extend ATF tests in t_trapsignal.sh to verify software breakpoint traps	2018-05-22 04:32:56 +00:00
lib	Refactor and enable the signal3 ATF ptrace(2) test	2018-05-20 23:47:16 +00:00
libexec	Avoid casting fun by switching ifunc helper functions to return	2018-03-09 20:15:03 +00:00
modules	Skip the test on non-modular kernels	2018-01-09 15:16:02 +00:00
net	Remove ping6_opts_hops, "-g" does not exist anymore (RH0 removed).	2018-04-26 06:23:33 +00:00
rump	Fix build	2017-12-28 07:46:34 +00:00
sbin	Make most of the resize_ffs tests skip if PUFFS is not configured	2017-10-08 21:12:27 +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	Typos.	2018-02-08 09:05:16 +00:00
usr.bin	Improve wording for non-native speakers of English	2018-05-04 12:51:18 +00:00
usr.sbin	Add test mtree -O with same hash value in directory and leaf.	2017-09-07 04:05:21 +00:00
h_macros.h	provide an RL variant that prints an extra argument	2016-08-20 15:49:08 +00:00
Makefile	Remove MKCRYPTO option.	2017-05-21 15:28:36 +00:00
Makefile.inc	better name	2017-01-14 01:33:32 +00:00
README

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.