public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asn at samba dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/30424] Calling dlopen from preinit function inhibits proper libc initialization Date: Thu, 02 Nov 2023 07:46:53 +0000 [thread overview] Message-ID: <bug-30424-131-lf7umyIHL5@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30424-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30424 --- Comment #1 from Andreas Schneider <asn at samba dot org> --- The libssh project uses cwrap [1] to run tests against the openssh sshd server. When trying to use AddressSanitizer with our test environment we ran into this issue [2]. Florian helped to debug the issue we see and tracked it down to this problem. We have environment variables to disable RTLD_DEEPBIND in the wrappers. However the envrion is empty somehow and we get RTLD_DEEPBIND: ==31700==You are trying to dlopen a libc.so.6 shared library with RTLD_DEEPBIND flag which is incompatible with sanitizer runtime (see https://github.com/google/sanitizers/issues/611 for details). If you want to run libc.so.6 library under sanitizers please remove RTLD_DEEPBIND from dlopen flags. It would be really great to run AddressSanitzer with our testsuite but we need this fixed. [1] https://cwrap.org [2] https://gitlab.com/cryptomilk/libssh-mirror/-/commits/asn-asan -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-11-02 7:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-05 19:59 [Bug dynamic-link/30424] New: " fweimer at redhat dot com 2023-05-05 20:03 ` [Bug dynamic-link/30424] " asn at samba dot org 2023-11-02 7:46 ` asn at samba dot org [this message] 2023-11-02 10:13 ` sam at gentoo dot 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-30424-131-lf7umyIHL5@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).