strace/test
Denys Vlasenko 68ba190f0a New test: test/many_looping_threads.c
Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
2015-03-21 20:59:39 +01:00
..
.gitignore New test: test/many_looping_threads.c 2015-03-21 20:59:39 +01:00
childthread.c Whitespace cleanups. no code changes. 2011-06-07 12:13:24 +02:00
clone.c test: include headers for used funcs 2013-05-02 22:41:50 +00:00
fork.c test: include headers for used funcs 2013-05-02 22:41:50 +00:00
leaderkill.c Whitespace cleanups. no code changes. 2011-06-07 12:13:24 +02:00
Makefile New test: test/many_looping_threads.c 2015-03-21 20:59:39 +01:00
many_looping_threads.c New test: test/many_looping_threads.c 2015-03-21 20:59:39 +01:00
mmap_offset_decode.c Clean up mmap decoding 2013-02-19 11:54:36 +01:00
mtd.c test: add mtd/ubi test helpers 2013-05-02 22:43:47 +00:00
procpollable.c Improve code readability by avoiding assignments inside if() 2011-08-23 12:53:01 +02:00
README test: add a manual test for seccomp decoding 2015-02-06 01:52:59 +00:00
seccomp.c test: add a manual test for seccomp decoding 2015-02-06 01:52:59 +00:00
sfd.c test/sfd.c: add missing includes 2015-02-20 13:21:40 +00:00
sig.c test: include headers for used funcs 2013-05-02 22:41:50 +00:00
sigkill_rain.c test: include headers for used funcs 2013-05-02 22:41:50 +00:00
skodic.c test/skodic: make a bit more portable 2013-05-01 14:54:05 +00:00
threaded_execve.c test/threaded_execve: fix on metag 2013-05-01 14:55:54 +00:00
ubi.c test: add mtd/ubi test helpers 2013-05-02 22:43:47 +00:00
vfork.c test: include headers for used funcs 2013-05-02 22:41:50 +00:00
wait_must_be_interruptible.c test: include headers for used funcs 2013-05-02 22:41:50 +00:00
x32_lseek.c Remove wrong x32-specific lseek 2013-02-17 13:17:49 +01:00
x32_mmap.c Fixes in "new" mmap 2013-02-18 03:13:07 +01:00

This directory contains some manual tests.
For automated tests, see ../tests/.

To run a test:
* Run make
* Run resulting executable(s) under strace
* Check strace output and/or program's output and exitcode

To add a new test:
* Add its .c source to this dir
* Add it to "all" and "clean" targets in Makefile
* Add it to .gitignore file

Please spend some time making your testcase understandable.
For example, it may print an explanation how it should be used
(which strace options to use, and what to look for in strace output).

If possible, make it so that your testcase detects error/bug
it is intended to test for, and prints error message and exits with 1
if the bug is detected, instead of relying on user to peruse strace output.