This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug malloc/22611] malloc might succeed and set errno to ENOMEM in case of heap allocation failure


https://sourceware.org/bugzilla/show_bug.cgi?id=22611

--- Comment #7 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Aurelien Jarno from comment #6)
> (In reply to Florian Weimer from comment #3)
> > (In reply to Aurelien Jarno from comment #0)
> > > tst-realloc tests, among others things that malloc and friends to not set
> > > errno to ENOMEM in case of successful memory allocation. This test always
> > > fail on sparc64 with "Error: errno is set but should not be".
> > 
> > Isn't this test invalid?

> Do you mean this is correct to set ENOMEM even when malloc is successful?

Yes, I think as long as we do not set errno to zero on success, we can clobber
errno.  POSIX explicitly says that applications should check errno only after
failure (or if the function specification provides additional scenarios where
it has a defined value).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]