|
From: Burton S. <BSt...@co...> - 2005-03-15 18:44:32
|
Yup it's 2.6 and yes, --sanity-level=0 worked around it.
Thanks!
-----Burton
-----Original Message-----
From: Jeremy Fitzhardinge [mailto:je...@go...]
Sent: Tuesday, March 15, 2005 11:29 AM
To: Burton Strauss
Cc: val...@li...
Subject: Re: [Valgrind-users] BUG(?) w/ setuid()/setgid() and threads ??
Burton Strauss wrote:
>However, 2.2 works fine w/o the parameter.
>
>It's hard to tell what's causing the error, as there is a lot of
>processing between the 'thread running' message and any subsequent log
messages.
>
Valgrind will periodically open /proc/self/maps to do some sanity checking.
If the thread changes its id so that it can't open its own /proc/self/maps,
then this will fail. You can use --sanity-level=0 to turn off the sanity
checking. I guess the proper fix would be for Valgrind to keep
/proc/self/maps open from the start in case it gets into a state where it
can't open it later (chroot would also cause this).
J
|