public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: uweigand@de.ibm.com To: gcc-gnats@gcc.gnu.org Subject: libgcj/8142: '$' in class names vs. dlopen 'dynamic string tokens' Date: Fri, 04 Oct 2002 06:36:00 -0000 [thread overview] Message-ID: <20021004132916.7232.qmail@sources.redhat.com> (raw) >Number: 8142 >Category: libgcj >Synopsis: '$' in class names vs. dlopen 'dynamic string tokens' >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: change-request >Submitter-Id: net >Arrival-Date: Fri Oct 04 06:36:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Ulrich Weigand >Release: gcc 3.3 >Organization: >Environment: Linux (glibc 2.x, x >= 1) >Description: libgcj passes class names to dlopen to find shared libraries implementing the class. In particular, in the case of inner classes, this name will contains '$' characters. However, the Linux dlopen implementation interprets '$' to signify a 'dynamic string token' that is subject to replacement. Currently, Linux implements the dynamic string tokens $ORIGIN and $PLATFORM. Thus, if an inner class happens to be named ORIGIN or PLATFORM, dlopen will substitute those strings, and either the intended shared library will not be found, or possibly even an incorrect library will be loaded. Furthermore, there is a bug in glibc 2.2.5 that causes dlopen to go into an endless loop if the path contains a '$' that is not followed by one of the recognized dynamic string tokens. This causes libgcj to hang whenever it tries to load an inner class. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-10-04 13:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-04 6:36 uweigand [this message] 2002-11-02 15:35 tromey
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=20021004132916.7232.qmail@sources.redhat.com \ --to=uweigand@de.ibm.com \ --cc=gcc-gnats@gcc.gnu.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).