Re: Possible QA issue in _valgrind_clean_assert

["Frank Ch. Eigler" <fche@xxxxxxxxxx>]

Hi -

brolley wrote:

> 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
> [...]
> 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

OK, this probably comes from some sort of setuid emulation side-effect
in valgrind, triggered by kenj's "sudo ... pmmgr ..." change.  The two
don't seem to play well with each other.  I'll poke at the test case
tomorrow to see if the sudo can be removed or valgrind placated.


- FChE