public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/15971] No interface for debugger access to libraries loaded with dlmopen Date: Sun, 19 Sep 2021 21:49:34 +0000 [thread overview] Message-ID: <bug-15971-131-oZex9nXoO1@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15971-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=15971 --- Comment #7 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by H.J. Lu <hjl@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=a93d9e03a31ec14405cb3a09aa95413b67067380 commit a93d9e03a31ec14405cb3a09aa95413b67067380 Author: H.J. Lu <hjl.tools@gmail.com> Date: Tue Aug 17 19:35:48 2021 -0700 Extend struct r_debug to support multiple namespaces [BZ #15971] Glibc does not provide an interface for debugger to access libraries loaded in multiple namespaces via dlmopen. The current rtld-debugger interface is described in the file: elf/rtld-debugger-interface.txt under the "Standard debugger interface" heading. This interface only provides access to the first link-map (LM_ID_BASE). 1. Bump r_version to 2 when multiple namespaces are used. This triggers the GDB bug: https://sourceware.org/bugzilla/show_bug.cgi?id=28236 2. Add struct r_debug_extended to extend struct r_debug into a linked-list, where each element correlates to an unique namespace. 3. Initialize the r_debug_extended structure. Bump r_version to 2 for the new namespace and add the new namespace to the namespace linked list. 4. Add _dl_debug_update to return the address of struct r_debug' of a namespace. 5. Add a hidden symbol, _r_debug_extended, for struct r_debug_extended. 6. Provide the symbol, _r_debug, with size of struct r_debug, as an alias of _r_debug_extended, for programs which reference _r_debug. This fixes BZ #15971. Reviewed-by: Florian Weimer <fweimer@redhat.com> -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-09-19 21:49 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-19 15:00 [Bug dynamic-link/15971] New: " gbenson at redhat dot com 2013-09-19 15:13 ` [Bug dynamic-link/15971] " carlos at redhat dot com 2013-09-19 15:13 ` carlos at redhat dot com 2013-09-27 12:19 ` jan.kratochvil at redhat dot com 2013-10-03 17:51 ` tromey at redhat dot com 2014-06-13 12:49 ` fweimer at redhat dot com 2015-02-12 11:27 ` stsp at users dot sourceforge.net 2015-02-12 12:30 ` mathieu.lacage at gmail dot com 2015-02-12 12:38 ` mathieu.lacage at gmail dot com 2015-03-27 13:54 ` fche at redhat dot com 2015-09-23 21:06 ` woodard at redhat dot com 2015-10-16 21:40 ` orion at cora dot nwra.com 2021-07-23 0:35 ` carlos at redhat dot com 2021-09-19 21:49 ` cvs-commit at gcc dot gnu.org [this message] 2021-09-19 22:04 ` hjl.tools at gmail 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-15971-131-oZex9nXoO1@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).