This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/22679] New: getcwd(3) can succeed without returning an absolute path
- From: "ldv at sourceware dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Fri, 05 Jan 2018 22:34:11 +0000
- Subject: [Bug libc/22679] New: getcwd(3) can succeed without returning an absolute path
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=22679
Bug ID: 22679
Summary: getcwd(3) can succeed without returning an absolute
path
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: ldv at sourceware dot org
CC: drepper.fsp at gmail dot com
Blocks: 18203
Target Milestone: ---
As noted in https://sourceware.org/bugzilla/show_bug.cgi?id=18203,
getcwd(3) on linux can succeed without returning an absolute path
because the underlying getcwd syscall, starting with linux commit
v2.6.36-rc1~96^2~2, may succeed without returning an absolute path.
This is a conformance issue because "The getcwd() function shall place
an absolute pathname of the current working directory in the array
pointed to by buf, and return buf".
Referenced Bugs:
https://sourceware.org/bugzilla/show_bug.cgi?id=18203
[Bug 18203] realpath() does not handle unreachable paths correctly
--
You are receiving this mail because:
You are on the CC list for the bug.