core: use syscall wrappers instead of direct syscalls - regression test

various xlators and other components are invoking system calls
directly instead of using the libglusterfs/syscall.[ch] wrappers.

If not using the system call wrappers there should be a comment
in the source explaining why the wrapper isn't used.

Change-Id: Id2207deb81a75e1af6f34bf857e74725f8bb532f
BUG: 1267967
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Reviewed-on: http://review.gluster.org/12410
Tested-by: NetBSD Build System <jenkins@build.gluster.org>
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Jeff Darcy <jdarcy@redhat.com>

1 files changed, 46 insertions, 0 deletions

diff --git a/tests/basic/0symbol-check.t b/tests/basic/0symbol-check.t
new file mode 100755
index 00000000000..d5b2ac4be86
--- /dev/null
+++ b/tests/basic/0symbol-check.t
@@ -0,0 +1,46 @@
+#!/bin/bash
+#
+
+. $(dirname $0)/../include.rc
+
+buildscratch=""
+
+case $OSTYPE in
+Linux)
+        ;;
+*)
+        echo "Skip Linux specific test" >&2
+        SKIP_TESTS
+        exit 0
+        ;;
+esac
+
+# look in the usual places for the build tree
+if [ -d /build/scratch ]; then
+        buildscratch="/build/scratch"
+else
+        # might be in developer's tree
+        if [ -d ./libglusterfs/src/.libs ]; then
+                buildscratch="."
+        elif [ -d ../libglusterfs/src/.libs]; then
+                buildscratch=".."
+        fi
+fi
+
+if [ -z ${buildscratch} ]; then
+        echo "could find build tree in /build/scratch, . or .." >&2
+        SKIP_TESTS
+        exit 0
+fi
+
+# check symbols
+
+rm -f ./.symbol-check-errors
+
+TEST find ${buildscratch} -name \*.o -exec ./tests/basic/symbol-check.sh {} \\\;
+
+TEST [ ! -e ./.symbol-check-errors ]
+
+rm -f ./.symbol-check-errors
+
+cleanup