|
From: <ric...@me...> - 2004-11-05 15:42:18
|
Google says it's a priority form of getmsg(). My linux man page says its unimplemented and obsolete. Nicholas Nethercote writes: In a message dated: Fri, 05 Nov 2004 12:06:20 GMT > Hi, > > I see the syscalls getpmsg() and putpmsg() in coregrind/vg_syscalls, but I > see almost nothing about them in the Linux source code -- __NR_getpmsg and > __NR_putpmsg are defined in asm-i386/unistd.h, but they don't appear in > any actual .c files. Does anyone know what they are and how they work? > > Thanks. > > N > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers -- Rich Coe ric...@me... General Electric Medical Systems |
|
From: Nicholas N. <nj...@ca...> - 2004-11-05 16:37:23
|
On Fri, 5 Nov 2004 ric...@me... wrote: > Google says it's a priority form of getmsg(). > > My linux man page says its unimplemented and obsolete. That's odd... system call wrappers have been added on demand, ie. when someone complains that Valgrind doesn't handle a particular syscall. So why would they have been added if they aren't used? Looking at the logs, Jeremy added it in revision 1.49 as part of a big change, so that doesn't help much. Thanks for the info. N |