Re: [Valgrind-users] Problem with REDIR

[Tom H. <to...@co...>]

In message <520...@BA...>
        Rakesh S. Shevde <Rak...@ge...> wrote:

> I am running 
> $ valgrind --version
> valgrind-3.2.1 
>
> $ nm -a memcheck | grep setprio
> 000000003803eca6 T vgSysWrap_generic_sys_setpriority_before

If you are getting that message then that is not the version you are
running - double check your path and make sure that you are running
the version that you think you are running.

Running with -d should also show you the path of the tool binary that
it is using.

There is no way that 3.2.1 should report the system call as unhandled
on amd64-linux as it is definitely hooked up to a handler.

> What happens if the syscall is not implemented say for setpriority
> The caller (in my case the exec I am testing) would get a return value
> as success or failure..

It would get an ENOSYS error.

> I am wondering if that is the cause for failure later with SIGSEGV.

I would think it unlikely, but as you haven't provided any details of
the SEGV it is hard to comment.

Tom

-- 
Tom Hughes (to...@co...)
http://www.compton.nu/