On 02/12/2015 12:01 AM, Nathan Scott wrote:
... could you take a look & work it out together? I'm punting its
something specific to Dave's valgrind version/installation. Also,
note I've had to update the valgrind-suppress change from the SASL
fix; syntax used was not available for older valgrinds (e.g. 3.6.0
on rhel6).
Here are the results from running: sudo strace -o /tmp/666.strace.txt -f
sh ./check 666
666 - output mismatch (see 666.out.bad)
18a19,21
> ==12100== could not unlink
/tmp/vgdb-pipe-from-vgdb-to-12100-by-root-on-brolley-t530
> ==12100== could not unlink
/tmp/vgdb-pipe-to-vgdb-from-12100-by-root-on-brolley-t530
> ==12100== could not unlink
/tmp/vgdb-pipe-shared-mem-vgdb-12100-by-root-on-brolley-t530
Within the generated log, we find:
12100
unlink("/tmp/vgdb-pipe-from-vgdb-to-12100-by-root-on-brolley-t530") = -1
EPERM (Operation not permitted)
and in the filesystem, we see:
prw-------. 1 root root 0 Feb 12 17:03
vgdb-pipe-to-vgdb-from-12100-by-root-on-brolley-t530
-rw-------. 1 root root 40 Feb 12 17:03
vgdb-pipe-shared-mem-vgdb-12100-by-root-on-brolley-t530
prw-------. 1 root root 0 Feb 12 17:03
vgdb-pipe-from-vgdb-to-12100-by-root-on-brolley-t530
I hope this helps,
Dave
|