summaryrefslogtreecommitdiffstats
path: root/testsuite/systemtap.syscall/umask.c
diff options
context:
space:
mode:
authorFrank Ch. Eigler <fche@elastic.org>2009-04-30 17:07:43 -0400
committerFrank Ch. Eigler <fche@elastic.org>2009-04-30 17:07:43 -0400
commit059cd9efbd82e1017406a7a290a2fb9f6bfb64f7 (patch)
tree8ab74af55066fd93c30682da09014aa81e3339ef /testsuite/systemtap.syscall/umask.c
parentc12f7fa15eec148307fa94f886b0673c1d0dd789 (diff)
downloadsystemtap-steved-059cd9efbd82e1017406a7a290a2fb9f6bfb64f7.tar.gz
systemtap-steved-059cd9efbd82e1017406a7a290a2fb9f6bfb64f7.tar.xz
systemtap-steved-059cd9efbd82e1017406a7a290a2fb9f6bfb64f7.zip
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.
Diffstat (limited to 'testsuite/systemtap.syscall/umask.c')
-rw-r--r--testsuite/systemtap.syscall/umask.c12
1 files changed, 6 insertions, 6 deletions
diff --git a/testsuite/systemtap.syscall/umask.c b/testsuite/systemtap.syscall/umask.c
index 5d13575f..0a3d0534 100644
--- a/testsuite/systemtap.syscall/umask.c
+++ b/testsuite/systemtap.syscall/umask.c
@@ -5,16 +5,16 @@
int main()
{
umask (0);
- // umask (00) = NNNN
+ //staptest// umask (00) = NNNN
umask (7);
- // umask (07) = 00
+ //staptest// umask (07) = 00
umask (077);
- // umask (077) = 07
+ //staptest// umask (077) = 07
umask (0666);
- // umask (0666) = 077
+ //staptest// umask (0666) = 077
umask (0777);
- // umask (0777) = 0666
+ //staptest// umask (0777) = 0666
umask (01777);
- // umask (01777) = 0777
+ //staptest// umask (01777) = 0777
return 0;
}