Re: [Valgrind-users] Problem with REDIR

[Shevde, R. S \(GE Healthcare\) <Rak...@ge...>]

I am running=20
$ valgrind --version
valgrind-3.2.1=20

$ nm -a memcheck | grep setprio
000000003803eca6 T vgSysWrap_generic_sys_setpriority_before

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

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


-----Original Message-----
From: val...@li...
[mailto:val...@li...] On Behalf Of Tom
Hughes
Sent: Tuesday, October 10, 2006 4:42 PM
To: val...@li...
Subject: Re: [Valgrind-users] Problem with REDIR

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

> It then complains about
>  --2983-- WARNING: unhandled syscall: 141
>  =3D=3D2983=3D=3D    at 0x124B8657: setpriority (in =
/lib64/libc-2.3.6.so)

You haven't said what version of valgrind you are using, but this system
call is implemented in 3.2.1 so it obviously isn't the latest.

> setpriority is present in the coregrind syscall implementations.

Correct, and is hooked up on amd64-linux, so if you are getting that
error you are not running the current code.

> Please let me know on why do we get these  REDIR (???) messages.

Those are normal, don't worry about them.

tom

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

------------------------------------------------------------------------
-
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDE
V
_______________________________________________
Valgrind-users mailing list
Val...@li...
https://lists.sourceforge.net/lists/listinfo/valgrind-users