|
From: <sv...@va...> - 2005-08-14 17:36:15
|
Author: njn
Date: 2005-08-14 18:36:07 +0100 (Sun, 14 Aug 2005)
New Revision: 4406
Log:
Clarify comment.
Modified:
trunk/coregrind/m_syswrap/syswrap-generic.c
Modified: trunk/coregrind/m_syswrap/syswrap-generic.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/coregrind/m_syswrap/syswrap-generic.c 2005-08-14 17:25:28 UTC (=
rev 4405)
+++ trunk/coregrind/m_syswrap/syswrap-generic.c 2005-08-14 17:36:07 UTC (=
rev 4406)
@@ -2871,8 +2871,12 @@
=20
PRE(sys_getcwd)
{
- // Note that the kernel version of getcwd() behaves quite differently=
to
- // the glibc one.
+ // Comment from linux/fs/dcache.c:
+ // NOTE! The user-level library version returns a character pointer=
.
+ // The kernel system call just returns the length of the buffer fil=
led
+ // (which includes the ending '\0' character), or a negative error
+ // value.
+ // Is this Linux-specific? If so it should be moved to syswrap-linux=
.c.
PRINT("sys_getcwd ( %p, %llu )", ARG1,(ULong)ARG2);
PRE_REG_READ2(long, "getcwd", char *, buf, unsigned long, size);
PRE_MEM_WRITE( "getcwd(buf)", ARG1, ARG2 );
|