aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc
diff options
context:
space:
mode:
authorGuinevere Larsen <guinevere@redhat.com>2025-06-06 11:59:24 -0300
committerGuinevere Larsen <guinevere@redhat.com>2025-06-16 17:17:15 -0300
commitd89a57526d1714a0030705145798e5499feef87e (patch)
treea0e73cad4ea1b6b71acb916eca2270111d89d4f6 /gdb/doc
parent62f1dbee49983c1820bc32015d2e8cd2d085c4dd (diff)
downloadbinutils-d89a57526d1714a0030705145798e5499feef87e.zip
binutils-d89a57526d1714a0030705145798e5499feef87e.tar.gz
binutils-d89a57526d1714a0030705145798e5499feef87e.tar.bz2
gdb/doc: Explain linker namespaces
Recent GDB commits added more features related to linker namespaces and documented them on the manual, but did not add a convenient way for a user to understand what they are. This commit adds a quick explanation of what they are. It also fixes the inconsistency of using "linker namespaces" and "linkage namespaces", by always using the first form to avoid user confusion. Approved-By: Eli Zaretskii <eliz@gnu.org>
Diffstat (limited to 'gdb/doc')
-rw-r--r--gdb/doc/gdb.texinfo23
1 files changed, 15 insertions, 8 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index d14777b..c41aa89 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -13106,15 +13106,15 @@ environment variable.
@vindex $_active_linker_namespaces@r{, convenience variable}
@item $_active_linker_namespaces
-Number of active linkage namespaces in the inferior. In systems with no
-support for linkage namespaces, this variable will always be set to @samp{1}.
+Number of active linker namespaces in the inferior (@pxref{Files}). In systems
+with no support for linker namespaces, this variable will always be set to
+@samp{1}.
@vindex $_linker_namespace@r{, convenience variable}
@item $_linker_namespace
-The namespace which contains the current location in the inferior. This
-returns @value{GDBN}'s internal numbering for the namespace. In systems with no
-support for linker namespaces, this variable will always be set to
-@samp{0}.
+The namespace which contains the current location in the inferior. This returns
+@value{GDBN}'s internal numbering for the namespace. In systems with no support
+for linker namespaces, this variable will always be set to @samp{0}.
@end table
@@ -22242,11 +22242,18 @@ be determined then the address range for the @code{.text} section from
the library will be listed. If the @code{.text} section cannot be
found then no addresses will be listed.
-On systems that support linkage namespaces, the output includes an
+On systems that support linker namespaces, the output includes an
additional column @code{NS} if the inferior has more than one active
-namespace when the command is used. This column the linkage namespace
+namespace when the command is used. This column the linker namespace
that the shared library was loaded into.
+@cindex linker namespaces
+@dfn{Linker namespaces} are a feature of some standard libraries, that allow
+shared objects to be loaded in isolated environment, eliminating the
+possibility that those objects may cross-talk. Each set of isolated
+shared objects is said to belong to a ``namespace'', and linker related
+actions such as relocations do not cross namespace boundaries.
+
@kindex info dll
@item info dll @var{regex}
This is an alias of @code{info sharedlibrary}.