public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/28487] Static application fault with dlopen library in rtld_malloc stubs
Date: Fri, 22 Oct 2021 11:04:50 +0000 [thread overview]
Message-ID: <bug-28487-131-JtximGqSIe@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28487-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28487
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
Just a quick note that since glibc 2.27 calling dlopen from a static executable
is deprecated. The intent is to fully support static linkage, but mixed static
and dynamic linkage will not be allowed. So while this works today, and we may
review exactly what happened in this test case, it will certainly not be
supported in the future.
Is there any reason you can't use a fully dynamic link for this application?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-10-22 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 3:15 [Bug libc/28487] New: " Houdek.Ryan@fex-emu.org
2021-10-22 11:04 ` carlos at redhat dot com [this message]
2021-10-22 11:39 ` [Bug libc/28487] " Houdek.Ryan@fex-emu.org
2021-11-16 9:13 ` 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-28487-131-JtximGqSIe@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: link
Be 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).