syscalls testsuite: use different escape sequence

The syscall testsuite uses embedded "// TEXT" markers in the .c files
to designate expected output, kind of like the "dg-" bunch in the gcc
test suite.  Unfortunately, "//" is not a unique prefix to systemtap
tests, and in particular it can occur in the system headers that will
be picked up with the "gcc -E -C ..." invocation in test.tcl.

So let's switch to "//staptest//".  test.tcl is also modified to
escape a few more mischevious regexp metacharacters that might sneak
past.

1 files changed, 6 insertions, 6 deletions

diff --git a/testsuite/systemtap.syscall/unlink.c b/testsuite/systemtap.syscall/unlink.c
index b0d00be8..33fe6157 100644
--- a/testsuite/systemtap.syscall/unlink.c
+++ b/testsuite/systemtap.syscall/unlink.c
@@ -14,22 +14,22 @@ int main()
   close (fd1);
   
   unlink("foobar1");
-  // unlink ("foobar1") = 0
+  //staptest// unlink ("foobar1") = 0
 
   unlink("foobar1");
-  // unlink ("foobar1") = -NNNN (ENOENT)
+  //staptest// unlink ("foobar1") = -NNNN (ENOENT)
 
   unlink("foobar2");
-  // unlink ("foobar2") = -NNNN (ENOENT)
+  //staptest// unlink ("foobar2") = -NNNN (ENOENT)
 
   unlink(0);
-  // unlink (NULL) = -NNNN (EFAULT)
+  //staptest// unlink (NULL) = -NNNN (EFAULT)
 
   unlink("..");
-  // unlink ("..") = -NNNN (EISDIR)
+  //staptest// unlink ("..") = -NNNN (EISDIR)
 
   unlink("");
-  // unlink ("") = -NNNN (ENOENT)
+  //staptest// unlink ("") = -NNNN (ENOENT)
 
   return 0;
 }