public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikulas at artax dot karlin.mff.cuni.cz" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug malloc/16810] New: malloc modifies errno on success Date: Sat, 05 Apr 2014 00:58:00 -0000 [thread overview] Message-ID: <bug-16810-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=16810 Bug ID: 16810 Summary: malloc modifies errno on success Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: malloc Assignee: unassigned at sourceware dot org Reporter: mikulas at artax dot karlin.mff.cuni.cz Host: arm-linux-gnueabihf Target: arm-linux-gnueabihf Build: arm-linux-gnueabihf Created attachment 7532 --> https://sourceware.org/bugzilla/attachment.cgi?id=7532&action=edit a simple program that demonstrates that malloc call succeeds and modifies errno When the brk syscall fails to extend the heap, glibc tries to allocate a new memory pool using mmap. If mmap succeeds, the block is successfuly allocated and returned to the caller - however, in this case, errno is set to ENOMEM. The attached program demonstrates the problem. The bug was reproduced on glibc-2.19 on Ununtu Trusy Tahr, glibc-2.13 on Debian Wheezy and glibc-2.11.3 on Debian Squeeze. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-04-05 0:58 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-05 0:58 mikulas at artax dot karlin.mff.cuni.cz [this message] 2014-04-05 6:57 ` [Bug malloc/16810] " schwab@linux-m68k.org 2014-06-12 19:46 ` fweimer at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-16810-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).