|
From: Michael R. <mr...@wi...> - 2005-12-02 16:36:56
|
> > >--__--__-- > >Message: 11 >To: val...@li... >Subject: Re: [Valgrind-users] EINTR on socket calls on Linux RHEL3 >From: Tom Hughes <to...@co...> >Organization: Just Me >Date: Thu, 01 Dec 2005 16:18:14 +0000 > >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/>http://www.compton.nu/ > > >--__--__-- > >Message: 12 >From: Julian Seward <js...@ac...> >To: val...@li... >Subject: Re: [Valgrind-users] EINTR on socket calls on Linux RHEL3 >Date: Thu, 1 Dec 2005 16:51:34 +0000 > > >> > So, the lesson is, don't use the installed one but always grab the latest >> > sources. >> >> Which 2.4.1 isn't... > >Not even slightly. Michael, try 3.1.0 and let us know what happens. > >J > 3.1.0 works fine too. It appears to just be a problem on the RHEL 3 distribution version. Many thanks for the help. |