From: Simon Marchi <simark@simark.ca>
To: Markus Metzger <markus.t.metzger@intel.com>, gdb-patches@sourceware.org
Cc: Lu@sourceware.org, Hongjiu <hongjiu.lu@intel.com>
Subject: Re: [PATCH v5 03/15] gdb, gdbserver: support dlmopen()
Date: Mon, 21 Jul 2025 16:41:16 -0400 [thread overview]
Message-ID: <2f5a89a5-95e0-44bb-aa47-755451dc0192@simark.ca> (raw)
In-Reply-To: <20220602132514.957983-4-markus.t.metzger@intel.com>
On 6/2/22 9:25 AM, Markus Metzger via Gdb-patches wrote:
> @@ -359,14 +370,35 @@ struct svr4_info
> probe_and_action->prob->address. */
> htab_up probes_table;
>
> - /* List of objects loaded into the inferior, used by the probes-
> - based interface. */
> - struct so_list *solib_list = nullptr;
> + /* List of objects loaded into the inferior per namespace, used by the
> + probes-based interface.
> +
> + The namespace is represented by the address of its corresponding
> + r_debug[_ext] object. We get the namespace id as agrument to the
> + 'reloc_complete' probe but we don't get it when scanning the load map
> + on attach.
> +
> + The r_debug[_ext] objects may move when ld.so itself moves. In that
> + case, we expect also the global _r_debug to move so we can detect
> + this and reload everything. The r_debug[_ext] objects are not
> + expected to move individually.
> +
> + The special entry zero is reserved for a linear list to support
> + gdbstubs that do not support namespaces. */
> + std::map<CORE_ADDR, so_list *> solib_lists;
Hi Markus (and others),
I'm currently doing some work inside solib-svr4.c, and I am puzzled by
the comments that say that _r_debug and ld.so can move.
I noticed that when starting the inferior, we try to read the shared
library list very early, before the dynamic linker had time to set the
DT_NEEDED slots. So at this point, we read read a debug base of 0. And
so we need to handle it changing from 0 to the value it will eventually
have.
But are there really use cases of ld.so relocating mid-execution? I
would have hoped that when we have a value for the default debug base,
we can assume that it won't change.
The only thing related to the debug base changing I found is this:
https://pi.simark.ca/gdb-patches/20080221014732.GA27568@caradoc.them.org/T/#rc0d0f322c8b484ecb620ec3d0d6263190e323182
But I wonder if it is still relevant today...
Thanks,
Simon
next prev parent reply other threads:[~2025-07-21 20:41 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 13:24 [PATCH v5 00/15] basic linker namespace support Markus Metzger via Gdb-patches
2022-06-02 13:25 ` [PATCH v5 01/15] gdb, testsuite: extend gdb_test_multiple checks Markus Metzger via Gdb-patches
2022-06-13 1:28 ` Kevin Buettner via Gdb-patches
2022-06-02 13:25 ` [PATCH v5 02/15] gdb, solib-svr4: remove locate_base() Markus Metzger via Gdb-patches
2022-06-02 23:04 ` Kevin Buettner via Gdb-patches
2022-06-02 13:25 ` [PATCH v5 03/15] gdb, gdbserver: support dlmopen() Markus Metzger via Gdb-patches
2022-06-19 4:02 ` Kevin Buettner via Gdb-patches
2022-06-27 12:55 ` Metzger, Markus T via Gdb-patches
2022-06-30 22:35 ` Kevin Buettner via Gdb-patches
2025-07-21 20:41 ` Simon Marchi [this message]
2025-07-22 7:07 ` Metzger, Markus T
2025-07-22 14:58 ` Simon Marchi
2022-06-02 13:25 ` [PATCH v5 04/15] gdbserver: move main_lm handling into caller Markus Metzger via Gdb-patches
2022-06-19 4:22 ` Kevin Buettner via Gdb-patches
2022-06-02 13:25 ` [PATCH v5 05/15] gdb, gdbserver: extend RSP to support namespaces Markus Metzger via Gdb-patches
2022-06-02 16:09 ` Eli Zaretskii via Gdb-patches
2022-06-19 4:32 ` Kevin Buettner via Gdb-patches
2022-06-02 13:25 ` [PATCH v5 06/15] gdb, compile: unlink objfile stored in module Markus Metzger via Gdb-patches
2022-06-23 17:20 ` Kevin Buettner via Gdb-patches
2022-06-02 13:25 ` [PATCH v5 07/15] gdb, python: use gdbarch_iterate_over_objfiles_in_search_order Markus Metzger via Gdb-patches
2022-06-24 17:18 ` Kevin Buettner via Gdb-patches
2022-06-02 13:25 ` [PATCH v5 08/15] gdb, ada: collect standard exceptions in all objfiles Markus Metzger via Gdb-patches
2022-06-24 17:26 ` Kevin Buettner via Gdb-patches
2022-07-18 16:49 ` Tom Tromey
2022-07-18 5:35 ` Metzger, Markus T via Gdb-patches
2022-09-14 8:19 ` Metzger, Markus T via Gdb-patches
2022-09-14 8:37 ` Joel Brobecker via Gdb-patches
2022-09-14 8:45 ` Metzger, Markus T via Gdb-patches
2022-06-02 13:25 ` [PATCH v5 09/15] gdb, ada: update ada_lookup_simple_minsym Markus Metzger via Gdb-patches
2022-06-24 23:42 ` Kevin Buettner via Gdb-patches
2022-07-18 17:02 ` Tom Tromey
2022-07-19 7:14 ` Metzger, Markus T via Gdb-patches
2022-09-14 8:19 ` Metzger, Markus T via Gdb-patches
2022-09-21 16:11 ` Tom Tromey
2022-06-02 13:25 ` [PATCH v5 10/15] gdb, ada: update ada_add_all_symbols Markus Metzger via Gdb-patches
2022-06-24 23:53 ` Kevin Buettner via Gdb-patches
2022-07-18 5:36 ` Metzger, Markus T via Gdb-patches
2022-07-18 16:56 ` Tom Tromey via Gdb-patches
2022-07-19 7:13 ` Metzger, Markus T via Gdb-patches
2022-07-19 12:23 ` Tom Tromey via Gdb-patches
2022-07-19 13:49 ` Metzger, Markus T via Gdb-patches
2022-06-02 13:25 ` [PATCH v5 11/15] gdb, cp: update add_symbol_overload_list_qualified Markus Metzger via Gdb-patches
2022-06-24 23:59 ` Kevin Buettner via Gdb-patches
2022-06-02 13:25 ` [PATCH v5 12/15] gdb, hppa: remove unused hppa_lookup_stub_minimal_symbol Markus Metzger via Gdb-patches
2022-06-25 0:01 ` Kevin Buettner via Gdb-patches
2022-06-02 13:25 ` [PATCH v5 13/15] gdb, symtab: inline find_quick_global_symbol_language Markus Metzger via Gdb-patches
2022-06-25 0:16 ` Kevin Buettner via Gdb-patches
2022-06-02 13:25 ` [PATCH v5 14/15] gdb: update gnu ifunc resolve Markus Metzger via Gdb-patches
2022-06-25 0:34 ` Kevin Buettner via Gdb-patches
2022-06-02 13:25 ` [PATCH v5 15/15] gdb, solib-svr4: support namespaces in DSO iteration Markus Metzger via Gdb-patches
2022-06-25 0:42 ` Kevin Buettner via Gdb-patches
2022-07-15 10:30 ` [PATCH v5 00/15] basic linker namespace support Metzger, Markus T via Gdb-patches
2022-07-16 0:04 ` Kevin Buettner via Gdb-patches
2022-07-18 5:33 ` Metzger, Markus T via Gdb-patches
2022-10-05 11:16 ` Metzger, Markus T via Gdb-patches
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=2f5a89a5-95e0-44bb-aa47-755451dc0192@simark.ca \
--to=simark@simark.ca \
--cc=Lu@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=hongjiu.lu@intel.com \
--cc=markus.t.metzger@intel.com \
/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