public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "Bjørn Mork via Libc-help" <libc-help@sourceware.org>
Cc: "Bjørn Mork" <bjorn@mork.no>
Subject: Re: What's the point having GLIBC_ABI_DT_RELR?
Date: Fri, 21 Jun 2024 13:56:10 +0200	[thread overview]
Message-ID: <87frt6wlut.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <87wmmia62l.fsf@miraculix.mork.no> (=?utf-8?Q?=22Bj=C3=B8rn?= Mork via Libc-help"'s message of "Fri, 21 Jun 2024 13:28:02 +0200")

* Bjørn Mork via Libc-help:

> [ dropped Peter's Cc as his email seems defunct ]
>
> Florian Weimer <fweimer@redhat.com> writes:
>> * Bjørn Mork via Libc-help:
>>
>>> Isn't the whole GLIBC_ABI_DT_RELR test just unnecessarily preventing
>>> glibc from loading libraries with DT_RELR?  Any glibc version testing
>>> for it will also support DT_RELR. So it would have worked fine if it
>>> weren't for the test.  Looks like unnecessary forced breakage - there
>>> must be something I'm missing. But what?
>>
>> The purpose of the check is to stop the proliferation of binaries that
>> crash when loaded by glibc versions that do not support DT_RELR.
>
> Thanks. Is this a crash on load, or will (some of) those binaries load
> successfully and then mysteriously crash later?

It's a mysterious crash.  Even with symbols and GDB, it's difficult to
figure out what is going on because the symptoms are quite unusual: some
pointers in global data are null because initialization has not been
performed.  These null pointers may end up at very distant places before
the crash.

Thanks,
Florian


      reply	other threads:[~2024-06-21 11:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21  7:56 Bjørn Mork
2024-06-21 11:14 ` Florian Weimer
2024-06-21 11:28   ` Bjørn Mork
2024-06-21 11:56     ` Florian Weimer [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=87frt6wlut.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=bjorn@mork.no \
    --cc=libc-help@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).