Am 24.09.22 um 04:24 schrieb Vasudev Kamath:
Hi Aurelien,
Old libc is because I reverted it as some scripts I use and autoconf as well
were breaking.
I assume I have mentioned in report that a downgrade solved crash. If I missed
sorry about that.
Sorry for top posting as I’m replying from my pho e
Sent from my iPhone
On 24-Sep-2022, at 03:21, Aurelien Jarno <aurel...@aurel32.net> wrote:
Hi,
On 2022-09-23 21:28, Bernhard Übelacker wrote:
On Fri, 23 Sep 2022 14:45:07 +0530 Vasudev Kamath <vasu...@debian.org> wrote:
Package: libc6
Version: 2.34-8
I upgraded libc6 to latest released 2.35-1
Module ld-linux-x86-64.so.2 with build-id
a03c3b14d371da908a3f22007b3f0c73d1f9f634
Module libc.so.6 with build-id
ef3afb43092687d7fcc8167fabdee73f4a3287f1
Module libgmp.so.10 with build-id
25c73b398493c695a013a6d9d493a8316aac0fa0
Module expr with build-id
b919757cbc30fbb64b14498222499d972fd80acd
Versions of packages libc6 suggests:
ii debconf [debconf-2.0] 1.5.79
pn glibc-doc <none>
ii libc-l10n 2.35-1
ii libnss-nis 3.1-4
ii libnss-nisplus 1.3-4
ii locales 2.35-1
Hello Vasudev,
I wonder if this libc6 installation is completed.
Because the bug report mentions version 2.34-8 from testing,
but e.g. locales and libc-l10n is 2.35-1.
Also searching for a package containing the debug information
for the build-id from the modules listing returns currently
the version 2.34-8 from testing.
But the build-id for ld-linux-x86-64.so.2 points to 2.35-1.
Maybe the libc package installation got interrupted?
Good catch. I also noticed that the libraries seems to be located in
/usr/lib/x86_64-linux-gnu/, which is typical of a usrmerge system, but
reportbug says "merged-usr: no".
Vasudev, you should probably check that you do not have too versions of
the glibc on your system, one in /lib/x86_64-linux-gnu/ and another one
in /usr/lib/x86_64-linux-gnu/ without the /lib -> usr/lib symlink.
Regards
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
Hello Vasudev,
ok, reverting back would explain reportbug using version 2.34-8.
But was this core taken at a time where all libc packages
should have been at 2.35-1 ?
Then I don't understand that "Module" line,
which shows the build-id from 2.34-8.
And if I understand you right the stack smashing
is from "autoreconf --version".
But I could not find it executing any "expr" processes in my test VM.
Kind regards,
Bernhard
