public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer 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: Tue, 16 Nov 2021 09:13:12 +0000	[thread overview]
Message-ID: <bug-28487-131-o3mzVmmjXX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28487-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28487

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com

--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
The issue here is the attempt to create a thread. This is very difficult to
support from a statically linked executable that has not been linked with
libpthread. Even if the statically linked binary has a sufficiently complete
copy of libpthread.a linked in, it will still need substantial glibc changes to
implement support for this. To be honest, I think we should spent our resources
on other efforts.

The binfmt_misc handler can be a shell script, it does not have to be the final
process running the binary. See Documentation/admin-guide/java.rst for an
example. You should use a shell script or a minimal static executable that
launches the actual interpreter, which can be dynamically linked. Use an
explicit loader invocation if necessary (in case the dynamically linked
interpreter does not have a usable PT_INTERP header for the chroot), and
perhaps adjust environment variables as needed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2021-11-16  9:13 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 ` [Bug libc/28487] " carlos at redhat dot com
2021-10-22 11:39 ` Houdek.Ryan@fex-emu.org
2021-11-16  9:13 ` fweimer at redhat dot com [this message]

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-o3mzVmmjXX@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).