Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Guinevere Larsen <guinevere@redhat.com>
To: gdb-patches@sourceware.org
Cc: Guinevere Larsen <guinevere@redhat.com>
Subject: [PATCH v2 0/3] Add some linker namespaces conveniences
Date: Wed,  9 Apr 2025 17:44:24 -0300	[thread overview]
Message-ID: <20250409204427.1680979-1-guinevere@redhat.com> (raw)

This series is a second step in improving the User Experience of
debugging inferiors with multiple namespaces. It adds 2 things to make
it more convenient for users to understand what the inferior is doing.

The first patch adds convenience variables, specifically
_active_linker_namespaces and _current_linker_namespaces. These can be
used to track where in the execution of an inferior the user is, and
could be used in breakpoint conditions to stop at a specific namespace.

The third patch adds a new command, "info linker-namespaces", to help the
user check what solibs are loaded, and where. To make the patch more
readable, the second patch is a minor refactor of the command "info
sharedlibrary".

The documentation changes have already been reviewed by Eli, changes for
v2 were minimal, only due to naming change.

Changes for v2:
* Renamed new command and variables to explicitly mention linker
  namespaces

Guinevere Larsen (3):
  gdb: add convenience variables around linker namespace debugging
  gdb: factor out printing a table of solibs for info sharedlibrary
  GDB: Introduce "info namespaces" command

 gdb/NEWS                                     |  11 +
 gdb/doc/gdb.texinfo                          |  28 ++
 gdb/solib-svr4.c                             |  55 ++++
 gdb/solib.c                                  | 267 ++++++++++++++-----
 gdb/solist.h                                 |   4 +
 gdb/testsuite/gdb.base/default.exp           |   2 +
 gdb/testsuite/gdb.base/dlmopen-ns-ids-main.c |   6 +
 gdb/testsuite/gdb.base/dlmopen-ns-ids.exp    | 148 ++++++++++
 8 files changed, 461 insertions(+), 60 deletions(-)


base-commit: a650cb6b2fbcd4ff02d2bd819d3979f3e57794b1
-- 
2.49.0


             reply	other threads:[~2025-04-09 20:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09 20:44 Guinevere Larsen [this message]
2025-04-09 20:44 ` [PATCH v2 1/3] gdb: add convenience variables around linker namespace debugging Guinevere Larsen
2025-04-12 23:49   ` Kevin Buettner
2025-04-13  0:22     ` Kevin Buettner
2025-04-09 20:44 ` [PATCH v2 2/3] gdb: factor out printing a table of solibs for info sharedlibrary Guinevere Larsen
2025-04-13  0:02   ` Kevin Buettner
2025-04-09 20:44 ` [PATCH v2 3/3] GDB: Introduce "info namespaces" command Guinevere Larsen
2025-04-13  0:20   ` Kevin Buettner
2025-04-14 12:13     ` Guinevere Larsen

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=20250409204427.1680979-1-guinevere@redhat.com \
    --to=guinevere@redhat.com \
    --cc=gdb-patches@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