public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "khuey at kylehuey dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug nptl/30670] New: libthread_db was not updated for the libpthreads removal Date: Sun, 23 Jul 2023 21:45:10 +0000 [thread overview] Message-ID: <bug-30670-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30670 Bug ID: 30670 Summary: libthread_db was not updated for the libpthreads removal Product: glibc Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: nptl Assignee: unassigned at sourceware dot org Reporter: khuey at kylehuey dot com CC: drepper.fsp at gmail dot com, tromey at sourceware dot org Target Milestone: --- With glibc 2.35 libpthreads.so was merged into libc itself. libthread_db, however, continues to have hardcoded references to libpthreads.so[0]. The API in question states that symbol lookups performed by the libthread_db consumer should be restricted to the provided DSO[1]. gdb, however, does not honor the DSO parameter[2], which is likely why this has not been noticed. Any libthread_db consumer attempting to faithfully follow the API contract is currently broken. [0] https://sourceware.org/git/?p=glibc.git;a=blob;f=nptl_db/thread_dbP.h;h=bf9ea27544d0fbd94c8abc1d6bc5821b9286c6a8;hb=HEAD#l155 [1] https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/nptl/proc_service.h;h=05bec74711c474feba772490be3e3f9aacea1d2e;hb=HEAD#l76 [2] Note the comment from the turn of the millennium: https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=gdb/proc-service.c;h=f735eb0ac812d5896c6a5ab846a7f7601447e894;hb=HEAD#l102 -- You are receiving this mail because: You are on the CC list for the bug.
reply other threads:[~2023-07-23 21:45 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-30670-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).