public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/11839] gdb does not detect calls to dlmopen
Date: Tue, 18 Oct 2022 13:24:54 +0000	[thread overview]
Message-ID: <bug-11839-4717-Ou8SZaOsmG@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11839-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=11839

--- Comment #7 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Markus Metzger <mmetzger@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8d56636a0ecbe6c38bf52b0683326ee21693c548

commit 8d56636a0ecbe6c38bf52b0683326ee21693c548
Author: Markus Metzger <markus.t.metzger@intel.com>
Date:   Mon Oct 4 10:24:35 2021 +0200

    gdb, gdbserver: support dlmopen()

    In glibc, the r_debug structure contains (amongst others) the following
    fields:

      int r_version:
        Version number for this protocol.  It should be greater than 0.

    If r_version is 2, struct r_debug is extended to struct r_debug_extended
    with one additional field:

      struct r_debug_extended *r_next;
        Link to the next r_debug_extended structure.  Each r_debug_extended
        structure represents a different namespace.  The first r_debug_extended
        structure is for the default namespace.

    1. Change solib_svr4_r_map argument to take the debug base.
    2. Add solib_svr4_r_next to find the link map in the next namespace from
    the r_next field.
    3. Update svr4_current_sos_direct to get the link map in the next namespace
    from the r_next field.
    4. Don't check shared libraries in other namespaces when updating shared
    libraries in a new namespace.
    5. Update svr4_same to check the load offset in addition to the name
    6. Update svr4_default_sos to also set l_addr_inferior
    7. Change the flat solib_list into a per-namespace list using the
    namespace's r_debug address to identify the namespace.

    Add gdb.base/dlmopen.exp to test this.

    To remain backwards compatible with older gdbserver, we reserve the
    namespace zero for a flat list of solibs from all namespaces.  Subsequent
    patches will extend RSP to allow listing libraries grouped by namespace.

    This fixes PR 11839.

    Co-authored-by: Lu, Hongjiu  <hongjiu.lu@intel.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-10-18 13:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11839-4717@http.sourceware.org/bugzilla/>
2011-05-17 13:18 ` gbenson at redhat dot com
2011-06-07 15:21 ` gbenson at redhat dot com
2011-07-31 19:14 ` ppluzhnikov at google dot com
2013-03-15  4:19 ` carlos at redhat dot com
2013-03-15 10:09 ` palves at redhat dot com
2013-09-19 15:02 ` gbenson at redhat dot com
2015-02-12 18:27 ` stsp at users dot sourceforge.net
2021-11-20 15:53 ` ppluzhnikov at google dot com
2022-10-18 13:24 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-24  2:53 ` tromey at sourceware 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-11839-4717-Ou8SZaOsmG@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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: link
Be 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).