Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"
Package: libc6 Version: 2.34-8 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I upgraded libc6 to latest released 2.35-1 * What exactly did you do (or not do) that was effective (or ineffective)? After upgrade noticed autoreconf --version was failing with **stack smashing detected** message. But in general looks like triggered by expr command. From the coredumpctl got following Message: Process 85280 (expr) of user 1000 dumped core. Module linux-vdso.so.1 with build-id c35c947b072ff69b395cd326b83b24630f2c5065 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 Stack trace of thread 85280: #0 0x7fbfabc8983c n/a (libc.so.6 + 0x8983c) #1 0x7fbfabc3da52 raise (libc.so.6 + 0x3da52) #2 0x7fbfabc28469 abort (libc.so.6 + 0x28469) #3 0x7fbfabc7dc18 n/a (libc.so.6 + 0x7dc18) #4 0x7fbfabd18c62 __fortify_fail (libc.so.6 + 0x118c62) #5 0x7fbfabd18c40 __stack_chk_fail (libc.so.6 + 0x118c40) #6 0x7fbfabc8449d n/a (libc.so.6 + 0x8449d) #7 0x7fbfac06c893 n/a (ld-linux-x86-64.so.2 + 0x20893) #8 0x7fbfac067f2f n/a (ld-linux-x86-64.so.2 + 0x1bf2f) #9 0x7fbfac069b21 n/a (ld-linux-x86-64.so.2 + 0x1db21) #10 0x7fbfac068948 n/a (ld-linux-x86-64.so.2 + 0x1c948) ELF object binary architecture: AMD x86-64 Back trace from gdb #0 0x7fbfabc8983c in ?? () from /usr/lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x7fbfabc8983c in ?? () from /usr/lib/x86_64-linux-gnu/libc.so.6 #1 0x7fbfabc3da52 in raise () from /usr/lib/x86_64-linux-gnu/libc.so.6 #2 0x7fbfabc28469 in abort () from /usr/lib/x86_64-linux-gnu/libc.so.6 #3 0x7fbfabc7dc18 in ?? () from /usr/lib/x86_64-linux-gnu/libc.so.6 #4 0x7fbfabd18c62 in __fortify_fail () from /usr/lib/x86_64-linux-gnu/libc.so.6 #5 0x7fbfabd18c40 in __stack_chk_fail () from /usr/lib/x86_64-linux-gnu/libc.so.6 #6 0x7fbfabc8449d in ?? () from /usr/lib/x86_64-linux-gnu/libc.so.6 #7 0x7fbfac06c893 in dl_main (phdr=, phnum=, user_entry=, auxv=) at ./elf/rtld.c:2562 #8 0x7fbfac067f2f in _dl_sysdep_start (start_argptr=start_argptr@entry=0x7ffdc5baaa40, dl_main=dl_main@entry=0x7fbfac069db0 ) at ../sysdeps/unix/sysv/linux/dl-sysdep.c:140 #9 0x7fbfac069b21 in _dl_start_final (arg=0x7ffdc5baaa40) at ./elf/rtld.c:507 #10 _dl_start (arg=0x7ffdc5baaa40) at ./elf/rtld.c:596 #11 0x7fbfac068948 in _start () from /lib64/ld-linux-x86-64.so.2 #12 0x0001 in ?? () #13 0x7ffdc5bacd78 in ?? () #14 0x in ?? () * What outcome did you expect instead? expr should not have crashed. I'm attaching the core file from the systemd-coredump. Also post this I downgraded libc6 to 2.34-8 from snapshots and no more crash is detected. If anything more is needed do let me know. Thanks and Regards Vasudev -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libc6 depends on: ii libgcc-s1 12.2.0-3 Versions of packages libc6 recommends: ii libidn2-0 2.3.3-1+b1 Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.79 pn glibc-doc ii libc-l10n 2.35-1 ii libnss-nis 3.1-4 ii libnss-nisplus 1.3-4 ii locales2.35-1 -- debconf information: glibc/upgrade: true glibc/restart-services: glibc/kernel-not-supported: * libraries/restart-without-asking: true glibc/disable-screensaver: glibc/restart-failed: glibc/kernel-too-old: core.expr.1000.d5ff83e0fd69439497afd17511de3417.85280.166392358300.zst Description: application/zstd
Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"
On Fri, 23 Sep 2022 14:45:07 +0530 Vasudev Kamath 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 ii libc-l10n 2.35-1 ii libnss-nis 3.1-4 ii libnss-nisplus 1.3-4 ii locales2.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? Kind regards, Bernhard [1] /usr/lib/debug/.build-id/ef/3afb43092687d7fcc8167fabdee73f4a3287f1.debug https://packages.debian.org/search?searchon=contents&keywords=3afb43092687d7fcc8167fabdee73f4a3287f1&mode=filename&suite=testing&arch=any [2] /usr/lib/debug/.build-id/a0/3c3b14d371da908a3f22007b3f0c73d1f9f634.debug https://packages.debian.org/search?searchon=contents&keywords=3c3b14d371da908a3f22007b3f0c73d1f9f634&mode=filename&suite=unstable&arch=any
Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"
Hi, On 2022-09-23 21:28, Bernhard Übelacker wrote: > On Fri, 23 Sep 2022 14:45:07 +0530 Vasudev Kamath 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 > > ii libc-l10n 2.35-1 > > ii libnss-nis 3.1-4 > > ii libnss-nisplus 1.3-4 > > ii locales2.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
Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"
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 wrote: > > Hi, > >> On 2022-09-23 21:28, Bernhard Übelacker wrote: >>> On Fri, 23 Sep 2022 14:45:07 +0530 Vasudev Kamath >>> 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 >>> ii libc-l10n 2.35-1 >>> ii libnss-nis 3.1-4 >>> ii libnss-nisplus 1.3-4 >>> ii locales2.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
Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"
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 wrote: Hi, On 2022-09-23 21:28, Bernhard Übelacker wrote: On Fri, 23 Sep 2022 14:45:07 +0530 Vasudev Kamath 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 ii libc-l10n 2.35-1 ii libnss-nis 3.1-4 ii libnss-nisplus 1.3-4 ii locales2.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
Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"
> 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. Ah sorry I did coredumpctl debug post reverting the libc6. But core file attached is taken when actual 2.35 was installed. > > 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. Actually just invoking autoconf was crashing and just executing expr itself was also crashing. If needed I can install latest libc and provide any required information. Do let me know Thanks and Regards Vasudev
Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"
control: notfound -1 glibc/2.34-8 control: found -1 glibc/2.35-1 Hello Vasudev, On 2022-09-24 21:18, Vasudev Kamath wrote: > > > 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. This mail should fix the BTS version. > Ah sorry I did coredumpctl debug post reverting the libc6. But core file > attached is taken when actual 2.35 was installed. I have looked at the coredump you sent me: $ eu-unstrip -n --core core.expr.1000.d5ff83e0fd69439497afd17511de3417.85280.166392358300 0x5604c0781000+0x1e000 b919757cbc30fbb64b14498222499d972fd80acd@0x5604c0781368 . - /usr/bin/expr 0x7fbfabc0+0x201000 ef3afb43092687d7fcc8167fabdee73f4a3287f1@0x7fbfabc00380 - - /usr/lib/x86_64-linux-gnu/libc.so.6 0x7ffdc5bde000+0x1000 c35c947b072ff69b395cd326b83b24630f2c5065@0x7ffdc5bde54c . - linux-vdso.so.1 0x7fbfac04c000+0x362b8 a03c3b14d371da908a3f22007b3f0c73d1f9f634@0x7fbfac04c248 /lib64/ld-linux-x86-64.so.2 - ld-linux-x86-64.so.2 0x7fbfabfc9000+0x80bc8 25c73b398493c695a013a6d9d493a8316aac0fa0@0x7fbfabfc9248 /usr/lib/x86_64-linux-gnu/libgmp.so.10 - libgmp.so.10 ef3afb43092687d7fcc8167fabdee73f4a3287f1 => comes from libc6 version 2.34-8 a03c3b14d371da908a3f22007b3f0c73d1f9f634 => comes from libc6 version 2.35-1 So the crash is likely due to a mismatch between glibc. I believe this is due to an issue with usrmerge as the paths reported by your core file seems to show that your system is merged, while reportbug says "merged-usr: no". By using a non usrmerged system, with libc6 2.34-8 duplicated in both /lib/x86_64-linux-gnu/ and /usr/lib/x86_64-linux-gnu, and upgrading it to libc6 2.35-1, I am able to reproduce your issue with expr: $ expr *** stack smashing detected ***: terminated Aborted > > 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. > > Actually just invoking autoconf was crashing and just executing expr itself > was also crashing. If needed I can install latest libc and provide any > required information. Do let me know Before trying to upgrade again, we should ensure your system is in a sane state. Could you please send us the output of: ls -ld /lib ls -l /lib/x86_64-linux-gnu/libc.so.6 ls -l /usr/lib/x86_64-linux-gnu/libc.so.6 Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"
> > I have looked at the coredump you sent me: > > $ eu-unstrip -n --core > core.expr.1000.d5ff83e0fd69439497afd17511de3417.85280.166392358300 > 0x5604c0781000+0x1e000 > b919757cbc30fbb64b14498222499d972fd80acd@0x5604c0781368 . - /usr/bin/expr > 0x7fbfabc0+0x201000 > ef3afb43092687d7fcc8167fabdee73f4a3287f1@0x7fbfabc00380 - - > /usr/lib/x86_64-linux-gnu/libc.so.6 > 0x7ffdc5bde000+0x1000 c35c947b072ff69b395cd326b83b24630f2c5065@0x7ffdc5bde54c > . - linux-vdso.so.1 > 0x7fbfac04c000+0x362b8 > a03c3b14d371da908a3f22007b3f0c73d1f9f634@0x7fbfac04c248 > /lib64/ld-linux-x86-64.so.2 - ld-linux-x86-64.so.2 > 0x7fbfabfc9000+0x80bc8 > 25c73b398493c695a013a6d9d493a8316aac0fa0@0x7fbfabfc9248 > /usr/lib/x86_64-linux-gnu/libgmp.so.10 - libgmp.so.10 > > ef3afb43092687d7fcc8167fabdee73f4a3287f1 > => comes from libc6 version 2.34-8 > a03c3b14d371da908a3f22007b3f0c73d1f9f634 > => comes from libc6 version 2.35-1 > > So the crash is likely due to a mismatch between glibc. I believe this > is due to an issue with usrmerge as the paths reported by your core file > seems to show that your system is merged, while reportbug says > "merged-usr: no". > > By using a non usrmerged system, with libc6 2.34-8 duplicated in both > /lib/x86_64-linux-gnu/ and /usr/lib/x86_64-linux-gnu, and upgrading it > to libc6 2.35-1, I am able to reproduce your issue with expr: > > $ expr > *** stack smashing detected ***: terminated > Aborted Interesting. I had put init-system-helpers on hold because it was reported with some issue and I see usrmerge package is not installed on my system. usrmerge: Installed: (none) Candidate: 31 Version table: 31 500 500 http://deb.debian.org/debian sid/main amd64 Packages 500 http://deb.debian.org/debian sid/main i386 Packages 30+nmu1 -1 100 /var/lib/dpkg/status >> > 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. >> >> Actually just invoking autoconf was crashing and just executing expr itself >> was also crashing. If needed I can install latest libc and provide any >> required information. Do let me know > > Before trying to upgrade again, we should ensure your system is in a > sane state. Could you please send us the output of: > > ls -ld /lib > ls -l /lib/x86_64-linux-gnu/libc.so.6 > ls -l /usr/lib/x86_64-linux-gnu/libc.so.6 └─(09:09:40 on master)──> ls -ld /lib ──(Mon,Sep26)─┘ drwxr-xr-x 9 root root 4096 Sep 23 14:37 /lib ┌─(~/.emacs.d)─(vasudeva.sk@bhrigu:pts/8)─┐ └─(09:12:50 on master)──> ls -l /lib/x86_64-linux-gnu/libc.so.6 ──(Mon,Sep26)─┘ -rwxr-xr-x 1 root root 2049032 Sep 11 03:35 /lib/x86_64-linux-gnu/libc.so.6 ┌─(~/.emacs.d)─(vasudeva.sk@bhrigu:pts/8)─┐ └─(09:13:06 on master)──> ls -l /usr/lib/x86_64-linux-gnu/libc.so.6 ──(Mon,Sep26)─┘ -rwxr-xr-x 1 root root 2049032 Sep 11 03:35 /usr/lib/x86_64-linux-gnu/libc.so.6 ┌─(~/.emacs.d)─ Is it that if I install usrmerge and then upgrade libc it should work? Thanks and Regards, Vasudev
Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"
Vasudev Kamath writes: > > └─(09:09:40 on master)──> ls -ld /lib > > ──(Mon,Sep26)─┘ > drwxr-xr-x 9 root root 4096 Sep 23 14:37 /lib > ┌─(~/.emacs.d)─(vasudeva.sk@bhrigu:pts/8)─┐ > └─(09:12:50 on master)──> ls -l /lib/x86_64-linux-gnu/libc.so.6 > > ──(Mon,Sep26)─┘ > -rwxr-xr-x 1 root root 2049032 Sep 11 03:35 /lib/x86_64-linux-gnu/libc.so.6 > ┌─(~/.emacs.d)─(vasudeva.sk@bhrigu:pts/8)─┐ > └─(09:13:06 on master)──> ls -l /usr/lib/x86_64-linux-gnu/libc.so.6 > > ──(Mon,Sep26)─┘ > -rwxr-xr-x 1 root root 2049032 Sep 11 03:35 > /usr/lib/x86_64-linux-gnu/libc.so.6 > ┌─(~/.emacs.d)─ > > Is it that if I install usrmerge and then upgrade libc it should work? Post installation of usrmerge this output is changed └─(09:37:07 on master)──> ls -ld /lib/x86_64-linux-gnu/libc.so.6 1 ↵ ──(Mon,Sep26)─┘ -rwxr-xr-x 1 root root 2061320 Sep 23 01:32 /lib/x86_64-linux-gnu/libc.so.6 ┌─(~/.emacs.d)─(vasudeva.sk@bhrigu:pts/8)─┐ └─(09:37:20 on master)──> ls -ld /usr/lib/x86_64-linux-gnu/libc.so.6 ──(Mon,Sep26)─┘ -rwxr-xr-x 1 root root 2049032 Sep 11 03:35 /usr/lib/x86_64-linux-gnu/libc.so.6 ┌─(~/.emacs.d)─(vasudeva.sk@bhrigu:pts/8)─┐ └─(09:37:25 on master)──> ls -ld /lib ──(Mon,Sep26)─┘ drwxr-xr-x 9 root root 4096 Sep 26 09:32 /lib ┌─(~/.emacs.d)─(vasudeva.sk@bhrigu:pts/8)─┐ └─(09:38:14 on master)──> So looks like my system is not in sane state. Do I need to just delete /usr/lib/ libc and try this?. Cheers, Vasudev
Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"
Vasudev Kamath writes: > Post installation of usrmerge this output is changed > > └─(09:37:07 on master)──> ls -ld /lib/x86_64-linux-gnu/libc.so.6 > > 1 ↵ ──(Mon,Sep26)─┘ > -rwxr-xr-x 1 root root 2061320 Sep 23 01:32 /lib/x86_64-linux-gnu/libc.so.6 > ┌─(~/.emacs.d)─(vasudeva.sk@bhrigu:pts/8)─┐ > └─(09:37:20 on master)──> ls -ld /usr/lib/x86_64-linux-gnu/libc.so.6 > > ──(Mon,Sep26)─┘ > -rwxr-xr-x 1 root root 2049032 Sep 11 03:35 > /usr/lib/x86_64-linux-gnu/libc.so.6 > ┌─(~/.emacs.d)─(vasudeva.sk@bhrigu:pts/8)─┐ > └─(09:37:25 on master)──> ls -ld /lib > > ──(Mon,Sep26)─┘ > drwxr-xr-x 9 root root 4096 Sep 26 09:32 /lib > ┌─(~/.emacs.d)─(vasudeva.sk@bhrigu:pts/8)─┐ > └─(09:38:14 on master)──> > > So looks like my system is not in sane state. Do I need to just delete > /usr/lib/ libc and try this?. From objdump -p output it looks like /lib version is the 2.35 3 0x00 0x069691b2 GLIBC_2.32 GLIBC_2.31 34 0x00 0x069691b3 GLIBC_2.33 GLIBC_2.32 35 0x00 0x069691b4 GLIBC_2.34 GLIBC_2.33 36 0x00 0x069691b5 GLIBC_2.35 GLIBC_2.34 37 0x00 0x0963cf85 GLIBC_PRIVATE GLIBC_2.35 and /usr/lib version is 2.34 GLIBC_2.30 33 0x00 0x069691b2 GLIBC_2.32 GLIBC_2.31 34 0x00 0x069691b3 GLIBC_2.33 GLIBC_2.32 35 0x00 0x069691b4 GLIBC_2.34 GLIBC_2.33 36 0x00 0x0963cf85 GLIBC_PRIVATE GLIBC_2.34 And post removing /usr/lib version of libc it seems to work fine and no crash is happening. └─(09:44:30 on master)──> expr 1 ↵ ──(Mon,Sep26)─┘ expr: missing operand Try 'expr --help' for more information. ┌─(~/.emacs.d)─(vasudeva.sk@bhrigu:pts/8)─┐ └─(09:44:39 on master)──> Cheers, Vasudev
Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"
Hi, On 2022-09-26 09:45, Vasudev Kamath wrote: > And post removing /usr/lib version of libc it seems to work fine and no > crash is happening. > > └─(09:44:30 on master)──> expr > > 1 ↵ ──(Mon,Sep26)─┘ > expr: missing operand > Try 'expr --help' for more information. > ┌─(~/.emacs.d)─(vasudeva.sk@bhrigu:pts/8)─┐ > └─(09:44:39 on master)──> Thanks for all the details. It's great that your system is now fixed. Do you have an idea why libc6 2.34 ended up in /usr/lib/x86_64-linux-gnu? I do not see any explanation from the glibc side. Did you attempt a usrmerge migration that failed after moving some files, or do you think it's unrelated? Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"
Aurelien Jarno writes: > Hi, > > On 2022-09-26 09:45, Vasudev Kamath wrote: >> And post removing /usr/lib version of libc it seems to work fine and no >> crash is happening. >> >> └─(09:44:30 on master)──> expr >> >> 1 ↵ ──(Mon,Sep26)─┘ >> expr: missing operand >> Try 'expr --help' for more information. >> ┌─(~/.emacs.d)─(vasudeva.sk@bhrigu:pts/8)─┐ >> └─(09:44:39 on master)──> > > Thanks for all the details. It's great that your system is now fixed. Do > you have an idea why libc6 2.34 ended up in /usr/lib/x86_64-linux-gnu? > I do not see any explanation from the glibc side. Did you attempt a > usrmerge migration that failed after moving some files, or do you think > it's unrelated? > I seriously did not have a clue why system was in this state. I had installed system back in 2019 and just keep updating. Also it was not just glibc, a whole bunch of packages were in this state and it took me a while to fix the entire system. (Had to write script to automate entire process). I don't remember me attempting to install usrmerge but not sure if it came via some dependency and failed to install. Feels weird why system was in such a state. Cheers, Vasudev