WT-2336 Add a test validating schema operations via file system call …

…monitoring (#3059)

Take advantage of the above to create a maintainable .run file that works
on systems without ftruncate. Use macros to avoid using so many #ifdefs.

When output differences are detected, report the output's line number (or
range of lines numbers we tried to match) to make it easier to diagnose
differences.

Add O_NOATIME to list of predefines to check.  The probe needs to be
compiled -D_GNU_SOURCE on Linux.  Use all probed variables in the symbol
table when looking at strace/dtruss output, as strace uses symbolic flag names.

build_posix/Make.subdirs

@@ -40,6 +40,7 @@ test/packing
 test/readonly
 test/recovery
 test/salvage
+test/syscall
 test/thread
 
 # Benchmark programs.

dist/s_python

@@ -17,10 +17,10 @@ test -s $t && {
 	echo '[tab] characters appear in Python scripts:'
 	cat $t
 }
-# Check Python coding standards: check for trailing semi-colons.
+# Check Python coding standards: check for uncommented trailing semi-colons.
 # Don't check too widely, there are third-party tools that fail this test as
 # well as scripts in this directory that output C code, and so fail the test.
-egrep ';$' `find lang test -name '*.py'`> $t
+egrep '^[^#]*;$' `find lang test -name '*.py'`> $t
 test -s $t && {
 	echo 'trailing semi-colons in selected Python code:'
 	cat $t

test/syscall/Makefile.am

@@ -0,0 +1,7 @@
+AM_CPPFLAGS = -I$(top_builddir) -I$(top_srcdir)/src/include
+LDADD = $(top_builddir)/libwiredtiger.la
+AM_LDFLAGS = -static
+noinst_PROGRAMS =
+
+test_wt2336_base_SOURCES = wt2336_base/main.c
+noinst_PROGRAMS += test_wt2336_base