Browse Source

Document that getcwd() and realpath() are built on system calls that

have a different calling convention than the standard function...as seen
in kdump output.
ok deraadt@ schwarze@
OPENBSD_6_6
guenther 5 years ago
parent
commit
5ecede4ab7
1 changed files with 16 additions and 2 deletions
  1. +16
    -2
      src/lib/libc/stdlib/realpath.3

+ 16
- 2
src/lib/libc/stdlib/realpath.3 View File

@ -28,9 +28,9 @@
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE. .\" SUCH DAMAGE.
.\" .\"
.\" $OpenBSD: realpath.3,v 1.21 2019/06/15 17:06:46 jmc Exp $
.\" $OpenBSD: realpath.3,v 1.22 2019/06/29 21:21:27 guenther Exp $
.\" .\"
.Dd $Mdocdate: June 15 2019 $
.Dd $Mdocdate: June 29 2019 $
.Dt REALPATH 3 .Dt REALPATH 3
.Os .Os
.Sh NAME .Sh NAME
@ -147,3 +147,17 @@ The
.Fn realpath .Fn realpath
function call first appeared in function call first appeared in
.Bx 4.4 . .Bx 4.4 .
.Pp
In
.Ox 6.6 ,
it was reimplemented on top of a
.Fn __realpath
system call whose calling convention differs from the standard
function by requiring
.Ar resolved
to not be
.Dv NULL
and by returning an integer,
zero on success and \-1 with corresponding errno on failure.
This is visible in the output of
.Xr kdump 1 .

Loading…
Cancel
Save