public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "andi-bz at firstfloor dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/13276] New: assertation failure in realloc when running out of virtual mappings Date: Sat, 08 Oct 2011 16:24:00 -0000 [thread overview] Message-ID: <bug-13276-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13276 Bug #: 13276 Summary: assertation failure in realloc when running out of virtual mappings Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper.fsp@gmail.com ReportedBy: andi-bz@firstfloor.org Classification: Unclassified When a process runs out of virtual mappings on Linux (more mmaps than vm.max_map_count) then munmap can fail because it may need to split a mapping. In this case when there is a realloc() it will get an assertation failure because it doesn't expect munmap to fail. Seen with gcc with a specific input file that fragments memory badly: lto1: malloc.c:3551: munmap_chunk: Assertion `ret == 0' failed. realloc should return NULL in this case, not assert. free should cleanly return. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2011-10-08 16:24 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-08 16:24 andi-bz at firstfloor dot org [this message] 2011-10-08 18:40 ` [Bug libc/13276] " bugdal at aerifal dot cx 2011-10-08 19:05 ` andi-bz at firstfloor dot org 2011-10-08 20:01 ` bugdal at aerifal dot cx 2011-10-08 20:01 ` bugdal at aerifal dot cx 2011-10-10 3:23 ` [Bug libc/13276] assertion " ppluzhnikov at google dot com 2011-10-29 20:40 ` drepper.fsp at gmail dot com 2014-06-27 11:53 ` 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-13276-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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).