[issue1394] [PATCH] getcwd(3) returns wrong error codes

[Stathis Kamperis (via DragonFly issue tracker)]

New submission from Stathis Kamperis <ekamperi at gmail.com>:

Salute.

getcwd(3) returns EINVAL if the supplied buffer length is 0 or 1 and ENOMEM
(duh!) if the length is greater than 1 but can't hold pathname + 1.

POSIX expects getcwd() to return EINVAL if length is 0 and ERANGE if length is
greater than 0 but less than pathname + 1.

I attach a patch to review.  I've built a kernel and running it at the moment.
So far nothing bro

----------
assignedto: Beket
files: getcwd.diff
messages: 6722
nosy: Beket
priority: bug
status: unread
title: [PATCH] getcwd(3) returns wrong error codes

_____________________________________________________
DragonFly issue tracker <bugs at lists.dragonflybsd.org>
<http://bugs.dragonflybsd.org/issue1394>
_____________________________________________________Attachment:
getcwd.diff
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bin00000.bin
Type: application/octet-stream
Size: 965 bytes
Desc: "Description: Binary data"
URL: <http://lists.dragonflybsd.org/pipermail/bugs/attachments/20090604/1347f81a/attachment-0016.bin>