From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Tom Tromey <tom@tromey.com>
Cc: Markus Metzger via Gdb-patches <gdb-patches@sourceware.org>
Subject: RE: [PATCH v4] gdb, gdbserver: support dlmopen()
Date: Wed, 9 Mar 2022 12:23:46 +0000 [thread overview]
Message-ID: <DM8PR11MB574939A2812CC3BACB9084D4DE0A9@DM8PR11MB5749.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87wnhdjxor.fsf@tromey.com>
Hello Tom,
>Markus> + /* There may be different instances of the same library, in different
>Markus> + namespaces. Each instance, however, must have been loaded at a
>Markus> + different address so its relocation offset would be different. */
>Markus> + const lm_info_svr4 *lmg = (const lm_info_svr4 *) gdb->lm_info;
>Markus> + const lm_info_svr4 *lmi = (const lm_info_svr4 *) inferior->lm_info;
>Markus> +
>Markus> + return (lmg->l_addr_inferior == lmi->l_addr_inferior);
>
>Can you explain how objfile handling works?
>
>I'd suspect that just a single objfile will be made for a given .so.
>But, if that comment is correct (I think it is) then that would be
>wrong, because an objfile has to know the correct runtime offset.
GDB creates separate objfile objects per instance. I placed a breakpoint at
symbol_file_add_with_addrs and compared the objfile * returned from
objfile::make().
See also the output of 'maint print objfiles':
[...]
Object file /users/mmetzger/gdb/build/dlmopen-fc35/gdb/testsuite/outputs/gdb.base/dlmopen/dlmopen-lib.1.so: Objfile at 0x4bec900, bfd at 0x4ee7f60, 19 minsyms
Psymtabs:
/users/mmetzger/gdb/git/gdb/testsuite/gdb.base/dlmopen-lib.c at 0x4d05200
Object file /users/mmetzger/gdb/build/dlmopen-fc35/gdb/testsuite/outputs/gdb.base/dlmopen/dlmopen-lib.1.so: Objfile at 0x4beee90, bfd at 0x4ee7f60, 19 minsyms
Psymtabs:
/users/mmetzger/gdb/git/gdb/testsuite/gdb.base/dlmopen-lib.c at 0x4d05200
[...]
Regards,
Markus.
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2022-03-09 12:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 14:28 Markus Metzger
2022-01-21 11:42 ` Metzger, Markus T
2022-03-01 19:10 ` Tom Tromey
2022-03-09 12:23 ` Metzger, Markus T [this message]
2022-03-03 18:32 ` Pedro Alves
2022-03-09 12:24 ` Metzger, Markus T
2022-03-09 14:15 ` Pedro Alves
2022-03-29 16:13 ` Metzger, Markus T
2022-04-08 12:40 ` Metzger, Markus T
2022-05-25 17:12 ` Kevin Buettner
2022-05-31 9:29 ` Metzger, Markus T
2022-05-31 18:44 ` Ben Woodard
2022-05-24 18:40 Ben Woodard
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=DM8PR11MB574939A2812CC3BACB9084D4DE0A9@DM8PR11MB5749.namprd11.prod.outlook.com \
--to=markus.t.metzger@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).