mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: musl@lists.openwall.com, d.dorau@avm.de,
	Hauke Mehrtens <hmehrtens@maxlinear.com>
Subject: Re: [musl] Tracking shared libraries in GDB not working?
Date: Wed, 18 Jan 2023 11:03:52 -0500	[thread overview]
Message-ID: <20230118160352.GH4163@brightrain.aerifal.cx> (raw)
In-Reply-To: <0a67d948-d348-94f7-9cac-cc81a052f76e@hauke-m.de>

On Wed, Jan 18, 2023 at 12:14:28AM +0100, Hauke Mehrtens wrote:
> On 1/10/23 21:02, Hauke Mehrtens wrote:
> >On 1/9/22 06:14, Rich Felker wrote:
> >>On Mon, Dec 20, 2021 at 09:54:40AM +0100, d.dorau@avm.de wrote:
> >>>Thanks for your thoughts. I used them to search for further
> >>>information and found
> >>>the missing piece:
> >>>
> >>>https://lists.yoctoproject.org/g/yocto/message/48584
> >>>
> >>>I applied that first patch
> >>>https://lists.yoctoproject.org/g/yocto/attachment/48584/0/0007-Teach-dynlink.c-about-DT_MIPS_RLD_MAP_REL.patch
> >>>
> >>>and apparently it seems to solve the issue. :-)
> >>>
> >>>I did a search on this mailing list and couldn't find this
> >>>patch mentioned here.
> >>>Maybe you can include this patch in a future release if you
> >>>think the solution is correct.
> >>
> >>Thanks! This patch is not correct as-is, because the value of
> >>DT_MIPS_RLD_MAP_REL is only meaningful on mips and could be reused on
> >>other archs. But I've whipped up what I think is a correct version of
> >>it here (attached), using the same approach as used for
> >>DT_MIPS_RLD_MAP already. If you get a chance, please let me know if it
> >>works.
> >>
> >>Rich
> >Hi Rich,
> >
> >I tried your attached patch on a mips32 be system and it worked.
> >With this patch gdb was able to find the shared libraries which
> >were loaded with dlopen(). I tested this on OpenWrt 19.07 with
> >musl 1.1.24 and gdb 8.3.1 using gdbserver.
> >
> >It would be nice if you could add it to upstream musl libc.
> >
> >Hauke
> Hi,
> 
> This is also working fine for me with recent OpenWrt master using
> musl 1.2.3, gcc 12.2 and gdb 12.1.

Thanks for the data points and for bumping this. I'll go ahead and
apply it.

Rich

      reply	other threads:[~2023-01-18 16:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 13:10 d.dorau
2021-12-15 15:20 ` Rich Felker
2021-12-20  8:54 ` d.dorau
2022-01-09  5:14   ` Rich Felker
2023-01-10 20:02     ` Hauke Mehrtens
2023-01-17 23:14       ` Hauke Mehrtens
2023-01-18 16:03         ` Rich Felker [this message]

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=20230118160352.GH4163@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=d.dorau@avm.de \
    --cc=hauke@hauke-m.de \
    --cc=hmehrtens@maxlinear.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).