public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "linjy0410 at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/29567] New: when `dlopen` glibc itself, it needs `__ctype_init` Date: Tue, 13 Sep 2022 08:17:57 +0000 [thread overview] Message-ID: <bug-29567-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29567 Bug ID: 29567 Summary: when `dlopen` glibc itself, it needs `__ctype_init` Product: glibc Version: unspecified Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: dynamic-link Assignee: unassigned at sourceware dot org Reporter: linjy0410 at gmail dot com Target Milestone: --- We met an issue that while `dlopen("libc.so.6")` and using dlsym to call the functions inside, some will crash because of ctype TLS is not initialized, e.g. `iconv` that uses `isspace` which would access ctype. By manual dlsym and calling `__ctype_init`, it can work normally. I'm not sure whether this is a bug or dlopen a glibc is not intended. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-09-13 8:17 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-13 8:17 linjy0410 at gmail dot com [this message] 2022-09-13 9:04 ` [Bug dynamic-link/29567] " fweimer at redhat dot com 2022-09-14 5:28 ` linjy0410 at gmail dot com 2022-09-14 7:03 ` 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-29567-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).