Menu
▾
▴
valgrind-users
|
From: Michael V. <mv...@cs...> - 2003-06-01 09:42:44
|
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 |
|
From: Benjamin L. <ben...@re...> - 2003-06-01 19:04:07
|
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/ __________________________________________________________________________ Preudhomme's Law of Window Cleaning: It's on the other side. |
|
From: Benjamin L. <ben...@re...> - 2003-06-01 20:08:03
|
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. |
|
From: Benjamin L. <ben...@re...> - 2003-06-01 20:25:26
|
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. |
|
From: Michael V. <mv...@cs...> - 2003-06-01 20:44:25
|
Hmmm... just downloaded and compiled the CVS version of valgrind. I get the same bug wrt syscall 252. I looked in vg_syscalls.c and there is no mention of system call 252. Mike > Date: Mon, 2 Jun 2003 06:07:49 +1000 > From: Benjamin Lee <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. > |
|
From: Benjamin L. <ben...@re...> - 2003-06-02 00:26:49
|
Stranger still. Anyway, I just thought I'd check... but it seems 1.9.6 has support for __NR_exit_group. [Mon, 2 Jun 2003 10:19:08 +1000] Home Sweet Home [ben@pov:/var/local/ben/a/valgrind-1.9.6]$ find -type f | xargs grep -n __NR_exit_group ./coregrind/vg_syscalls.c:470:# if defined(__NR_exit_group) ./coregrind/vg_syscalls.c:471: case __NR_exit_group: ./coregrind/vg_scheduler.c:1472:# if defined(__NR_exit_group) ./coregrind/vg_scheduler.c:1473: || VG_(threads)[tid].m_eax == __NR_exit_group ./coregrind/vg_scheduler.c:1511:# if defined(__NR_exit_group) ./coregrind/vg_scheduler.c:1512: && VG_(threads)[tid].m_eax != __NR_exit_group [Mon, 2 Jun 2003 10:19:21 +1000] Home Sweet Home [ben@pov:/var/local/ben/a/valgrind-1.9.6]$ I'd suggest using Debian sid/unstable with dselect to install valgrind 1.9.6 rather than bother with compiling your own. But I'd say the problem will definitely be mismatched headers. Also... I checked my CVS files... [Mon, 2 Jun 2003 10:15:20 +1000] Home Sweet Home [ben@pov:~/cvsremote/valgrind]$ cvs status ./coregrind/vg_syscalls.c ./coregrind/vg_scheduler.c =================================================================== File: vg_syscalls.c Status: Up-to-date Working revision: 1.34 Repository revision: 1.34 /cvsroot/valgrind/valgrind/coregrind/vg_syscalls.c,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) =================================================================== File: vg_scheduler.c Status: Up-to-date Working revision: 1.126 Repository revision: 1.126 /cvsroot/valgrind/valgrind/coregrind/vg_scheduler.c,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) [Mon, 2 Jun 2003 10:15:39 +1000] Home Sweet Home [ben@pov:~/cvsremote/valgrind]$ [Mon, 2 Jun 2003 10:13:29 +1000] Home Sweet Home [ben@pov:~/cvsremote/valgrind]$ grep -n 252 /usr/include/asm/unistd.h 259:#define __NR_exit_group 252 [Mon, 2 Jun 2003 10:13:55 +1000] Home Sweet Home [ben@pov:~/cvsremote/valgrind]$ find -type f | xargs grep -n __NR_exit_group ./coregrind/vg_scheduler.c:1479:# if defined(__NR_exit_group) ./coregrind/vg_scheduler.c:1480: || VG_(threads)[tid].m_eax == __NR_exit_group ./coregrind/vg_scheduler.c:1518:# if defined(__NR_exit_group) ./coregrind/vg_scheduler.c:1519: && VG_(threads)[tid].m_eax != __NR_exit_group ./coregrind/vg_syscalls.c:470:# if defined(__NR_exit_group) ./coregrind/vg_syscalls.c:471: case __NR_exit_group: [Mon, 2 Jun 2003 10:14:17 +1000] Home Sweet Home [ben@pov:~/cvsremote/valgrind]$ On Monday, 2003-06-02 at 06:44:23 AM, Michael Vanier scribbled: > > Hmmm... just downloaded and compiled the CVS version of valgrind. I get > the same bug wrt syscall 252. I looked in vg_syscalls.c and there is no > mention of system call 252. > > Mike > > > Date: Mon, 2 Jun 2003 06:07:49 +1000 > > From: Benjamin Lee <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. > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users -- Benjamin Lee Melbourne, Australia "Always real." http://realthought.net/ __________________________________________________________________________ Don't worry about the world coming to an end today. It's already tomorrow in Australia. -- Charles Schulz |
|
From: Benjamin L. <ben...@re...> - 2003-06-02 00:33:05
|
One correction... the Debian package is found in testing not unstable. testing/main valgrind 1.9.6-1 [785kB] On Monday, 2003-06-02 at 10:26:20 AM, Benjamin Lee scribbled: > Stranger still. > > Anyway, I just thought I'd check... but it seems 1.9.6 has support for > __NR_exit_group. > > [Mon, 2 Jun 2003 10:19:08 +1000] Home Sweet Home > [ben@pov:/var/local/ben/a/valgrind-1.9.6]$ find -type f | xargs grep -n __NR_exit_group > ./coregrind/vg_syscalls.c:470:# if defined(__NR_exit_group) > ./coregrind/vg_syscalls.c:471: case __NR_exit_group: > ./coregrind/vg_scheduler.c:1472:# if defined(__NR_exit_group) > ./coregrind/vg_scheduler.c:1473: || VG_(threads)[tid].m_eax == __NR_exit_group > ./coregrind/vg_scheduler.c:1511:# if defined(__NR_exit_group) > ./coregrind/vg_scheduler.c:1512: && VG_(threads)[tid].m_eax != __NR_exit_group > [Mon, 2 Jun 2003 10:19:21 +1000] Home Sweet Home > [ben@pov:/var/local/ben/a/valgrind-1.9.6]$ > > > I'd suggest using Debian sid/unstable with dselect to install valgrind > 1.9.6 rather than bother with compiling your own. > > But I'd say the problem will definitely be mismatched headers. > > > > > > Also... I checked my CVS files... > > [Mon, 2 Jun 2003 10:15:20 +1000] Home Sweet Home > [ben@pov:~/cvsremote/valgrind]$ cvs status ./coregrind/vg_syscalls.c ./coregrind/vg_scheduler.c > =================================================================== > File: vg_syscalls.c Status: Up-to-date > > Working revision: 1.34 > Repository revision: 1.34 /cvsroot/valgrind/valgrind/coregrind/vg_syscalls.c,v > Sticky Tag: (none) > Sticky Date: (none) > Sticky Options: (none) > > =================================================================== > File: vg_scheduler.c Status: Up-to-date > > Working revision: 1.126 > Repository revision: 1.126 /cvsroot/valgrind/valgrind/coregrind/vg_scheduler.c,v > Sticky Tag: (none) > Sticky Date: (none) > Sticky Options: (none) > > [Mon, 2 Jun 2003 10:15:39 +1000] Home Sweet Home > [ben@pov:~/cvsremote/valgrind]$ > > > [Mon, 2 Jun 2003 10:13:29 +1000] Home Sweet Home > [ben@pov:~/cvsremote/valgrind]$ grep -n 252 /usr/include/asm/unistd.h > 259:#define __NR_exit_group 252 > [Mon, 2 Jun 2003 10:13:55 +1000] Home Sweet Home > [ben@pov:~/cvsremote/valgrind]$ find -type f | xargs grep -n __NR_exit_group > ./coregrind/vg_scheduler.c:1479:# if defined(__NR_exit_group) > ./coregrind/vg_scheduler.c:1480: || VG_(threads)[tid].m_eax == __NR_exit_group > ./coregrind/vg_scheduler.c:1518:# if defined(__NR_exit_group) > ./coregrind/vg_scheduler.c:1519: && VG_(threads)[tid].m_eax != __NR_exit_group > ./coregrind/vg_syscalls.c:470:# if defined(__NR_exit_group) > ./coregrind/vg_syscalls.c:471: case __NR_exit_group: > [Mon, 2 Jun 2003 10:14:17 +1000] Home Sweet Home > [ben@pov:~/cvsremote/valgrind]$ > > > On Monday, 2003-06-02 at 06:44:23 AM, Michael Vanier scribbled: > > > > Hmmm... just downloaded and compiled the CVS version of valgrind. I get > > the same bug wrt syscall 252. I looked in vg_syscalls.c and there is no > > mention of system call 252. > > > > Mike > > > > > Date: Mon, 2 Jun 2003 06:07:49 +1000 > > > From: Benjamin Lee <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/ __________________________________________________________________________ "I assure you the thought never even crossed my mind, lord." "Indeed? Then if I were you I'd sue my face for slander." -- Terry Pratchett, "The Colour of Magic" |
|
From: Michael V. <mv...@cs...> - 2003-06-02 00:46:48
|
Glad to hear it ;-) I didn't want to move to the unstable distribution just for this. I installed it and all is working smoothly again. Thanks for your help! Mike > Date: Mon, 2 Jun 2003 10:32:49 +1000 > From: Benjamin Lee <ben...@re...> > > One correction... the Debian package is found in testing not unstable. > > testing/main valgrind 1.9.6-1 [785kB] > > On Monday, 2003-06-02 at 10:26:20 AM, Benjamin Lee scribbled: > > Stranger still. > > > > Anyway, I just thought I'd check... but it seems 1.9.6 has support for > > __NR_exit_group. > > > > [Mon, 2 Jun 2003 10:19:08 +1000] Home Sweet Home > > [ben@pov:/var/local/ben/a/valgrind-1.9.6]$ find -type f | xargs grep -n __NR_exit_group > > ./coregrind/vg_syscalls.c:470:# if defined(__NR_exit_group) > > ./coregrind/vg_syscalls.c:471: case __NR_exit_group: > > ./coregrind/vg_scheduler.c:1472:# if defined(__NR_exit_group) > > ./coregrind/vg_scheduler.c:1473: || VG_(threads)[tid].m_eax == __NR_exit_group > > ./coregrind/vg_scheduler.c:1511:# if defined(__NR_exit_group) > > ./coregrind/vg_scheduler.c:1512: && VG_(threads)[tid].m_eax != __NR_exit_group > > [Mon, 2 Jun 2003 10:19:21 +1000] Home Sweet Home > > [ben@pov:/var/local/ben/a/valgrind-1.9.6]$ > > > > > > I'd suggest using Debian sid/unstable with dselect to install valgrind > > 1.9.6 rather than bother with compiling your own. > > > > But I'd say the problem will definitely be mismatched headers. > > > > > > > > > > > > Also... I checked my CVS files... > > > > [Mon, 2 Jun 2003 10:15:20 +1000] Home Sweet Home > > [ben@pov:~/cvsremote/valgrind]$ cvs status ./coregrind/vg_syscalls.c ./coregrind/vg_scheduler.c > > =================================================================== > > File: vg_syscalls.c Status: Up-to-date > > > > Working revision: 1.34 > > Repository revision: 1.34 /cvsroot/valgrind/valgrind/coregrind/vg_syscalls.c,v > > Sticky Tag: (none) > > Sticky Date: (none) > > Sticky Options: (none) > > > > =================================================================== > > File: vg_scheduler.c Status: Up-to-date > > > > Working revision: 1.126 > > Repository revision: 1.126 /cvsroot/valgrind/valgrind/coregrind/vg_scheduler.c,v > > Sticky Tag: (none) > > Sticky Date: (none) > > Sticky Options: (none) > > > > [Mon, 2 Jun 2003 10:15:39 +1000] Home Sweet Home > > [ben@pov:~/cvsremote/valgrind]$ > > > > > > [Mon, 2 Jun 2003 10:13:29 +1000] Home Sweet Home > > [ben@pov:~/cvsremote/valgrind]$ grep -n 252 /usr/include/asm/unistd.h > > 259:#define __NR_exit_group 252 > > [Mon, 2 Jun 2003 10:13:55 +1000] Home Sweet Home > > [ben@pov:~/cvsremote/valgrind]$ find -type f | xargs grep -n __NR_exit_group > > ./coregrind/vg_scheduler.c:1479:# if defined(__NR_exit_group) > > ./coregrind/vg_scheduler.c:1480: || VG_(threads)[tid].m_eax == __NR_exit_group > > ./coregrind/vg_scheduler.c:1518:# if defined(__NR_exit_group) > > ./coregrind/vg_scheduler.c:1519: && VG_(threads)[tid].m_eax != __NR_exit_group > > ./coregrind/vg_syscalls.c:470:# if defined(__NR_exit_group) > > ./coregrind/vg_syscalls.c:471: case __NR_exit_group: > > [Mon, 2 Jun 2003 10:14:17 +1000] Home Sweet Home > > [ben@pov:~/cvsremote/valgrind]$ > > > > > > On Monday, 2003-06-02 at 06:44:23 AM, Michael Vanier scribbled: > > > > > > Hmmm... just downloaded and compiled the CVS version of valgrind. I get > > > the same bug wrt syscall 252. I looked in vg_syscalls.c and there is no > > > mention of system call 252. > > > > > > Mike > > > > > > > Date: Mon, 2 Jun 2003 06:07:49 +1000 > > > > From: Benjamin Lee <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/ > > __________________________________________________________________________ > "I assure you the thought never even crossed my mind, lord." > "Indeed? Then if I were you I'd sue my face for slander." > -- Terry Pratchett, "The Colour of Magic" > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X