public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Houdek.Ryan@fex-emu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/28487] New: Static application fault with dlopen library in rtld_malloc stubs Date: Fri, 22 Oct 2021 03:15:01 +0000 [thread overview] Message-ID: <bug-28487-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28487 Bug ID: 28487 Summary: Static application fault with dlopen library in rtld_malloc stubs Product: glibc Version: 2.33 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: Houdek.Ryan@fex-emu.org CC: drepper.fsp at gmail dot com Target Milestone: --- Created attachment 13731 --> https://sourceware.org/bugzilla/attachment.cgi?id=13731&action=edit Test application. In some instances when a static/static-pie application does a dlopen on a shared library, the shared library will attempt to use the rtld_malloc stubs. These stub symbols are expected to be setup by the original application being loaded. Since we were a static application, these symbols aren't ever setup for something that the shared library to see. A likely workaround is that when the dynamic linker is loaded with the initial dlopen that `__rtld_malloc_init_real` should be called at some point. Sadly I'm having a hard time debugging this locally myself so I'm looking for help. I have a simple test application that compiles the main application elf as static-pie, then it loads a dynamic library that creates a thread. The act of creating a thread tries to use the rtld_malloc symbols. This was the easiest way I could find something that uses these malloc routines. This is attached as source. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-10-22 3:15 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-22 3:15 Houdek.Ryan@fex-emu.org [this message] 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
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@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).