X-Git-Url: http://git.ozlabs.org/?p=ccan;a=blobdiff_plain;f=ccan%2Ffailtest%2F_info;h=a9189a238fcdb363e3882f93d3333e4200438bb5;hp=73aa6a2daef21d92d48afd68833f5e5f40ad191f;hb=f18b792838ee010b42091639b673c7b28606aa47;hpb=f0002cb9e4f6f403a25ad50252c06694439900f0

diff --git a/ccan/failtest/_info b/ccan/failtest/_info
index 73aa6a2d..a9189a23 100644
--- a/ccan/failtest/_info
+++ b/ccan/failtest/_info
@@ -8,7 +8,8 @@
  * The failtest module overrides various standard functions, and forks
  * your unit test at those points to test failure paths.  The failing
  * child are expected to fail (eg. when malloc fails), but should not
- * leak memory or crash.
+ * leak memory or crash.  After including failtest_override.h, you can
+ * include failtest_restore.h to return to non-failing versions.
  *
  * The unit test is a normal CCAN tap-style test, except it should
  * start by calling failtest_init() and end by calling
@@ -26,7 +27,7 @@
  *
  *	int main(int argc, char *argv[])
  *	{
- *		void *a, *b;
+ *		char *a, *b;
  *
  *		failtest_init(argc, argv);
  *		plan_tests(3);
@@ -62,6 +63,8 @@ int main(int argc, char *argv[])
 	if (strcmp(argv[1], "depends") == 0) {
 		printf("ccan/compiler\n");
 		printf("ccan/read_write_all\n");
+		printf("ccan/build_assert\n");
+		printf("ccan/time\n");
 		return 0;
 	}