Re: [Valgrind-users] missing syscall: 252

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

For what it's worth...

ben@dbox:~$ dpkg -s libc6-dev
Package: libc6-dev
Status: install ok installed
Priority: standard
Section: libdevel
Installed-Size: 11748
Maintainer: GNU Libc Maintainers <deb...@li...>
Source: glibc
Version: 2.3.1-17
Replaces: man-db (<= 2.3.10-41), gettext (<= 0.10.26-1), ppp (<= 2.2.0f-24), libgdbmg1-dev (<= 1.7.3-24), ldso (<= 1.9.11-9), netkit-rpc, netbase (<< 4.0)
Provides: libc-dev
Depends: libc6 (= 2.3.1-17)
Recommends: c-compiler
Suggests: glibc-doc
Conflicts: libstdc++2.10-dev (<< 1:2.95.2-15), gcc-2.95 (<< 1:2.95.3-9), libpthread0-dev, libdl1-dev, libdb1-dev, libgdbm1-dev, libc6-dev (<< 2.0.110-1), locales (<< 2.1.3-5), libstdc++2.9-dev, netkit-rpc, libc-dev
Description: GNU C Library: Development Libraries and Header Files.
 Contains the symlinks, headers, and object files needed to compile
 and link programs which use the standard C library.

ben@dbox:~$ grep 252 /usr/include/asm/unistd.h
#define __NR_exit_group         252
ben@dbox:~$

ben@dbox:~/cvsremote/valgrind$ uname -a
Linux dbox 2.4.20-3-386 #1 Sun May 18 18:18:12 EST 2003 i686 GNU/Linux
ben@dbox:~/cvsremote/valgrind$

This box just compiled the latest CVS version, no problemo.

Good luck.
Cheers,
Ben.

On Monday, 2003-06-02 at 06:07:49 AM, Benjamin Lee scribbled:
> 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.

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

__________________________________________________________________________
Real Users know your home telephone number.