From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: Pedro Alves <palves@redhat.com>,
"xe-linux-external\(mailer list\)" <xe-linux-external@cisco.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"Jeremy Stenglein \(jstengle\)" <jstengle@cisco.com>
Subject: Re: [RFC PATCH 0/3] implement dlmopen hooks for gdb
Date: Thu, 17 Sep 2020 09:53:30 -0400 [thread overview]
Message-ID: <5ce2d889-9eea-4c53-8bba-d8216f2bf513@redhat.com> (raw)
In-Reply-To: <871rj0imo8.fsf@oldenburg2.str.redhat.com>
On 9/17/20 8:59 AM, Florian Weimer wrote:
> * Carlos O'Donell:
>
>> You will always have .dynsym with a definition for _r_debug_dlmopen.
>
> Note that this doesn't work if you just have a core file. In order to
> find _r_debug (or _r_debug_dlmopen), a debugger needs the exact same
> copy of ld.so that was used by the executable, otherwise the symbol
> cannot be found in the image.
You are correct.
I followed up on my own email regarding this.
So in the end to get process and core file debugging we'll need:
* _r_debug_dlmopen
* DT_DEBUG_DLMOPEN
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-09-17 13:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 19:32 [RFC PATCH 0/3] implement dlmopen hooks for gdb Daniel Walker via Libc-alpha
2020-06-26 21:17 ` Carlos O'Donell via Libc-alpha
2020-07-23 18:40 ` Daniel Walker (danielwa) via Libc-alpha
2020-07-23 21:20 ` Carlos O'Donell via Libc-alpha
2020-09-16 16:18 ` Daniel Walker (danielwa) via Libc-alpha
2020-09-17 12:52 ` Carlos O'Donell via Libc-alpha
2020-09-17 12:59 ` Florian Weimer via Libc-alpha
2020-09-17 13:53 ` Carlos O'Donell via Libc-alpha [this message]
2020-09-18 15:35 ` Daniel Walker (danielwa) via Libc-alpha
2020-09-18 15:40 ` Florian Weimer via Libc-alpha
2020-09-21 20:02 ` Daniel Walker (danielwa) via Libc-alpha
2021-07-28 18:33 ` Daniel Walker via Libc-alpha
2021-07-28 18:48 ` H.J. Lu via Libc-alpha
2020-09-17 13:52 ` Carlos O'Donell via Libc-alpha
2020-09-22 17:06 ` Florian Weimer via Libc-alpha
2020-09-22 17:28 ` Carlos O'Donell via Libc-alpha
2020-09-22 17:37 ` Florian Weimer via Libc-alpha
2020-09-22 17:59 ` Carlos O'Donell via Libc-alpha
2020-09-22 18:04 ` Florian Weimer via Libc-alpha
2020-09-22 18:41 ` Carlos O'Donell via Libc-alpha
2020-09-22 18:44 ` Florian Weimer via Libc-alpha
2020-09-22 18:46 ` Carlos O'Donell via Libc-alpha
2020-09-22 18:17 ` Andreas Schwab
2020-09-22 19:13 ` Carlos O'Donell via Libc-alpha
2020-06-26 21:30 ` Florian Weimer via Libc-alpha
2020-06-27 1:10 ` Daniel Walker (danielwa) via Libc-alpha
2020-07-02 13:54 ` Conan Huang (conhuang) via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5ce2d889-9eea-4c53-8bba-d8216f2bf513@redhat.com \
--to=libc-alpha@sourceware.org \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=jstengle@cisco.com \
--cc=palves@redhat.com \
--cc=xe-linux-external@cisco.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).