Bug#1004577: ldconfig -p coredumps
- To: Florian Weimer <fweimer@redhat.com>
- Cc: 1004577@bugs.debian.org
- Subject: Bug#1004577: ldconfig -p coredumps
- From: Christoph Berg <myon@debian.org>
- Date: Fri, 25 Mar 2022 21:11:43 +0100
- Message-id: <Yj4h/7DImA7FV4GB@msg.df7cb.de>
- Reply-to: Christoph Berg <myon@debian.org>, 1004577@bugs.debian.org
- In-reply-to: <87pmo6373m.fsf@oldenburg.str.redhat.com>
- References: <YfbTDYycLUk8X31u@msg.df7cb.de> <87pmo6373m.fsf@oldenburg.str.redhat.com> <YfbTDYycLUk8X31u@msg.df7cb.de>
Re: Florian Weimer
> > Package: libc-bin
> > Version: 2.33-3
> > Severity: important
> >
> > In https://salsa.debian.org/python-team/packages/python-telethon/-/jobs/2413916
> > there is a diff generated between the two builds because a core file
> > from `ldconfig -p` appears as /usr/lib/python3.10/dist-packages/core.
>
> Is this the “FATAL: kernel too old” error?
I guess it is, yes.
> We could remove this check from upstream, and just try to run code and
> see how far we get. I assume that these days, the check does more harm
> than good. People with pre-3.2 kernels (glibc's built-in baseline) will
> likely run a heavily patched 2.6.32 kernel, and that should be *almost*
> there.
That would fix the problem, yes.
Christoph
Reply to: