public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bruno at clisp dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug malloc/17924] 'free' should not set errno Date: Sat, 19 Dec 2020 19:30:51 +0000 [thread overview] Message-ID: <bug-17924-131-8LLeMjYzVh@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17924-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17924 Bruno Haible <bruno at clisp dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bruno at clisp dot org --- Comment #2 from Bruno Haible <bruno at clisp dot org> --- Created attachment 13064 --> https://sourceware.org/bugzilla/attachment.cgi?id=13064&action=edit Test case for one of the scenarios Find attached a test case for one of the scenarios, namely when 1. free() invokes munmap() and 2. munmap()'s attempt to split a VMA fails due to /proc/sys/vm/max_map_count. It fails on glibc 2.3.2, 2.23, 2.28, 2.32, as well as on musl libc 1.1.24. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-12-19 19:30 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-04 0:06 [Bug malloc/17924] New: " eggert at gnu dot org 2015-02-06 9:19 ` [Bug malloc/17924] " fweimer at redhat dot com 2020-12-19 19:30 ` bruno at clisp dot org [this message] 2020-12-19 21:05 ` eggert at cs dot ucla.edu 2020-12-19 22:02 ` bruno at clisp dot org 2020-12-19 23:31 ` eggert at cs dot ucla.edu 2020-12-21 7:15 ` eggert at cs dot ucla.edu 2020-12-23 5:28 ` eggert at cs dot ucla.edu 2020-12-24 0:28 ` eggert at cs dot ucla.edu 2020-12-29 8:47 ` eggert at cs dot ucla.edu 2023-12-29 11:10 ` gabravier at gmail 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-17924-131-8LLeMjYzVh@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).