Re: [Valgrind-users] missing syscall: 252

[Benjamin L. <ben...@re...>]

Another guess... maybe the compile was using the wrong kernel headers?

On Monday, 2003-06-02 at 05:26:49 AM, Michael Vanier scribbled:
> 
> Curious... I *tried* to do that but gave up after many attempts and went
> back to 2.4.17 (at least I thought so...).  Anyway, thanks for the advice.
> 
> Mike
> 
> > From: Benjamin Lee <ben...@re...>
> > Date: Mon, 2 Jun 2003 05:03:52 +1000
> > 
> > Hi,
> > 
> > The new syscall __NR_exit_group / 252 was added to kernel 2.4.20. I'd guess
> > you probably just upgraded your Debian Linux kernel from 2.4.18 to 2.4.20
> > using sid/unstable.
> > 
> > Roll yourself a valgrind from CVS and you'll be fine.
> > 
> > On Sunday, 2003-06-01 at 07:42:43 PM, Michael Vanier scribbled:
> > > 
> > > I just upgraded my valgrind installation to 1.9.6 from 1.9.5, and I
> > > immediately ran into a major problem.  I can't run valgrind any more
> > > because of a missing system call.  To add insult to injury, the number of
> > > the call (252) is not listed in /usr/include/asm/unistd.h.  Recompiling
> > > 1.9.5 fails as well with the same message, so presumably it's happening
> > > because the version of gcc/g++ I'm using has changed (I'm running gcc/g++
> > > 3.2.3 on a Debian Linux system).  Any advice/hints?
> > > 
> > > Mike
> > > 
> > 

-- 
Benjamin Lee
Melbourne, Australia             "Always real."    http://realthought.net/

__________________________________________________________________________
Real Users know your home telephone number.