Re: [Valgrind-users] Error with running valgrind against code with 'system' call

[Tom H. <th...@cy...>]

In message <76C...@us...>
        Tim Lee <TL...@ft...> wrote:

> ==3526== 
> Hello World
> proxy 3534 for tid 1 exited status -1, res 0
> got signal 17 in LWP 3526 (3526)
>  
> valgrind: vg_signals.c:1558 (vg_async_signalhandler): Assertion
> `vgPlain_ksigismember(&uc->uc_sigmask, sigNo)' failed.
> ==3526==    at 0x401749FE: (within
> /VIEWS/fes620_DEV630_linux.vws/.s/00027/8000015a3ffc7001valgrind.so)
>  
> sched status:
>  
> Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0
> ==3526==    at 0x40257BA0: sigprocmask (in /lib/libc-2.2.4.so)
> ==3526==    by 0x402788F0: __libc_system (in /lib/libc-2.2.4.so)
> ==3526==    by 0x80484B2: main (vtest.c:4)
>  
> Here is a test program I wrote to produce the above error:
>  
> int main ()
> {
>   printf ("Hello World\n");
>   system ("ls >/tmp/junk");
> }

I've tried this example on my systems and so far I've been unable to
reproduce the symptoms. On RedHat 9 I can't get it to fail and on
RedHat 7.2 it does fail sometimes, but with a different assertion:

valgrind: vg_proxylwp.c:973 (proxy_wait): Assertion `*status == proxy->exitcode' failed.
==31647==    at 0x40175546: (within /usr/lib/valgrind/valgrind.so)
==31647==    by 0x40175545: assert_fail (vg_mylibc.c:1161)
==31647==    by 0x401755A2: vgPlain_core_assert_fail (vg_mylibc.c:1172)
==31647==    by 0x40179087: proxy_wait (vg_proxylwp.c:973)
                                                                                                       
sched status:
                                                                                                       
Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0
==31647==    at 0x402F871A: __execve (../sysdeps/unix/sysv/linux/execve.c:70)
==31647==    by 0x4028C991: __libc_system (../sysdeps/posix/system.c:109)
==31647==    by 0x80484F2: main (71053.c:7)

Tom

-- 
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/