This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/18588] crypt "leaks" ENOENT
- From: "akshay.moghe at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 24 Jun 2015 07:22:06 +0000
- Subject: [Bug libc/18588] crypt "leaks" ENOENT
- Auto-submitted: auto-generated
- References: <bug-18588-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18588
Akshay <akshay.moghe at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Akshay <akshay.moghe at gmail dot com> ---
> Could you elaborate, please, why "leaking" of ENOENT by crypt(3) is a bug?
The manpage states that "a function that succeeds is allowed to change errno",
so based on that this isn't a bug. Hence I'm closing this out.
Background: I ran into this in a unit test suite where I explicitly clear the
errno before calling crypt, but find it to be set after crypt returns
successfully. It is a minor annoyance that a failed fips check on my regular
(couldnt-care-less-about-fips) laptop machine causes this behavior, hence I
filed the issue (maybe a little too soon).
--
You are receiving this mail because:
You are on the CC list for the bug.