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

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

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

> 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");
> }

This looks similar to bug 71053 which we haven't had a good test
case for until now.

Tom

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