diff options
| author | Frank Ch. Eigler <fche@elastic.org> | 2009-04-30 17:07:43 -0400 |
|---|---|---|
| committer | Frank Ch. Eigler <fche@elastic.org> | 2009-04-30 17:07:43 -0400 |
| commit | 059cd9efbd82e1017406a7a290a2fb9f6bfb64f7 (patch) | |
| tree | 8ab74af55066fd93c30682da09014aa81e3339ef /testsuite/systemtap.syscall/sync.c | |
| parent | c12f7fa15eec148307fa94f886b0673c1d0dd789 (diff) | |
| download | systemtap-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/sync.c')
| -rw-r--r-- | testsuite/systemtap.syscall/sync.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/testsuite/systemtap.syscall/sync.c b/testsuite/systemtap.syscall/sync.c index 637bc197..d6e22203 100644 --- a/testsuite/systemtap.syscall/sync.c +++ b/testsuite/systemtap.syscall/sync.c @@ -13,13 +13,13 @@ int main() fd = creat("foobar",S_IREAD|S_IWRITE); sync(); - // sync () = 0 + //staptest// sync () = 0 fsync(fd); - // fsync (NNNN) = 0 + //staptest// fsync (NNNN) = 0 fdatasync(fd); - // fdatasync (NNNN) = 0 + //staptest// fdatasync (NNNN) = 0 close(fd); |