Re: [Valgrind-users] EINTR on socket calls on Linux RHEL3

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

In message <a06100545bfb4cc256a9d@[10.100.2.144]>
        Michael Rutman <mr...@wi...> wrote:

> At 7:47 AM -0800 12/1/05, Duncan Sands wrote:
>>
>>> I'm not sure why an EINTR is being issued.  The call to socket shouldn't
>>> ever be returning that according to the man page.
>>
>>Is it the kernel or libc that generates the EINTR?
>>
>
> Sorry for wasting everyone's time.  I was using the valgrind installed on
> RHEL 3.

Oh right. I was kind of assuming we were talking valgrind 3 at least.

> I pulled the sources for valgrind 2.4.1 to see if it was throwing the
> exception and it works fine.
>
> So, the lesson is, don't use the installed one but always grab the latest
> sources.

Which 2.4.1 isn't...

Tom 

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