strace

Files

Denys Vlasenko 8158e7716c Update test/* directory, it seem to be a bit bit-rotted

Added README; modified sigkill_rain.c to be more understandable,
made clone.c compile; added wait_must_be_interruptible.c test;
updated Makefile and .gitignore.

Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>

2011-06-08 14:08:59 +02:00

.gitignore

Update test/* directory, it seem to be a bit bit-rotted

2011-06-08 14:08:59 +02:00

childthread.c

Whitespace cleanups. no code changes.

2011-06-07 12:13:24 +02:00

clone.c

Update test/* directory, it seem to be a bit bit-rotted

2011-06-08 14:08:59 +02:00

fork.c

By Hans-Christian Egtvedt (hans-christian.egtvedt AT atmel.com):

2009-02-25 14:24:02 +00:00

leaderkill.c

Whitespace cleanups. no code changes.

2011-06-07 12:13:24 +02:00

Makefile

Update test/* directory, it seem to be a bit bit-rotted

2011-06-08 14:08:59 +02:00

procpollable.c

By Hans-Christian Egtvedt (hans-christian.egtvedt AT atmel.com):

2009-02-25 14:24:02 +00:00

README

Update test/* directory, it seem to be a bit bit-rotted

2011-06-08 14:08:59 +02:00

sfd.c

By Hans-Christian Egtvedt (hans-christian.egtvedt AT atmel.com):

2009-02-25 14:24:02 +00:00

sig.c

By Hans-Christian Egtvedt (hans-christian.egtvedt AT atmel.com):

2009-02-25 14:24:02 +00:00

sigkill_rain.c

Update test/* directory, it seem to be a bit bit-rotted

2011-06-08 14:08:59 +02:00

skodic.c

Whitespace cleanups. no code changes.

2011-06-07 12:13:24 +02:00

vfork.c

By Hans-Christian Egtvedt (hans-christian.egtvedt AT atmel.com):

2009-02-25 14:24:02 +00:00

wait_must_be_interruptible.c

Update test/* directory, it seem to be a bit bit-rotted

2011-06-08 14:08:59 +02:00

README

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.