From: Tom de Vries <tdevries@suse.de>
To: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] [gdb] Work around zero l_addr/l_ld
Date: Fri, 11 Sep 2026 17:06:51 +0200 [thread overview]
Message-ID: <3fdd9c67-f13a-4ecc-9a99-599098fd38c7@suse.de> (raw)
In-Reply-To: <1b400ad2-969c-44e8-82cd-e0738a82a3d6@suse.de>
On 9/4/26 9:44 PM, Tom de Vries wrote:
>> My take on this would be no, it's not worth the complexity. It sounds
>> like the problem is caused by a glibc that has back-ported one part of a
>> fix, but missed the second part. I would suggest that a better solution
>> would be to raise a bug against the downstream glibc port and get them
>> to back-port the second part of the fix (commit 88361b408b).
>
> Hi Andrew,
>
> thanks for the review.
>
> Your reasoning makes sense, and I can live with it.
>
> I've submitted a bug ( https://bugs.almalinux.org/view.php?id=667 ).
And I've submitted a patch (
https://sourceware.org/pipermail/gdb-patches/2026-September/230275.html
) to detect this situation and bail out.
Thanks,
- Tom
prev parent reply other threads:[~2026-09-11 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 7:14 Tom de Vries
2026-09-02 16:31 ` [PING][RFC] " Tom de Vries
2026-09-04 13:07 ` [RFC] " Andrew Burgess
2026-09-04 19:44 ` Tom de Vries
2026-09-11 15:06 ` Tom de Vries [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=3fdd9c67-f13a-4ecc-9a99-599098fd38c7@suse.de \
--to=tdevries@suse.de \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
/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