public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/30452] LD_PREFER_MAP_32BIT_EXEC does not work with 2MiB load segment alignment Date: Wed, 17 May 2023 18:38:05 +0000 [thread overview] Message-ID: <bug-30452-131-JCE7N3kqVJ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30452-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30452 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hjl.tools at gmail dot com --- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> --- This won't work with 2MB page size: mmap(NULL, 6291464, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f11bce7f000 mmap(0x7f11bd000000, 4194312, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0) = 0x7f11bd000000 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-05-17 18:38 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-16 14:13 [Bug dynamic-link/30452] New: elf/tst-map-32bit-1a fails with binutils-2.30-117.el8.x86_64 fweimer at redhat dot com 2023-05-16 14:16 ` [Bug dynamic-link/30452] LD_PREFER_MAP_32BIT_EXEC does not work with 2MiB load segment alignment fweimer at redhat dot com 2023-05-17 18:38 ` hjl.tools at gmail dot com [this message] 2023-05-17 18:45 ` fweimer at redhat dot com 2023-05-17 20:16 ` hjl.tools at gmail dot com 2023-05-18 17:22 ` hjl.tools at gmail dot com 2023-06-30 17:43 ` cvs-commit at gcc dot gnu.org
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-30452-131-JCE7N3kqVJ@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).