[gentoo-user] ldconfig segfaults after updating to 23.0 profil

[gentoo-user] ldconfig segfaults after updating to 23.0 profil

[Dan Johansson]

Hello,

After updating my system to a 23.0 profile, default/linux/amd64/23.0/split-usr/desktop/plasma (stable), ldconfig has started segfaulting.

Here are the last few lines of "strace ldconfig":
newfstatat(AT_FDCWD, "/usr/lib/rust/lib/librustc_driver-131b866216b2910c.so", {st_mode=S_IFREG|0644, st_size=153456592, ...}, 0) = 0
openat(AT_FDCWD, "/usr/lib/llvm/17/lib", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3
fstat(3, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
getdents64(3, 0x5555572629d0 /* 22 entries */, 32768) = 824
newfstatat(AT_FDCWD, "/usr/lib/llvm/17/lib/libclang.so.17", {st_mode=S_IFREG|0755, st_size=17506304, ...}, 0) = 0
openat(AT_FDCWD, "/usr/lib/llvm/17/lib/libclang.so.17", O_RDONLY) = 4
fstat(4, {st_mode=S_IFREG|0755, st_size=17506304, ...}) = 0
mmap(NULL, 17506304, PROT_READ, MAP_SHARED, 4, 0) = 0x7fb6eb2d3000
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x7fb6ed37c4dc} ---
+++ killed by SIGSEGV +++
Segmentation fault

The file in question (I think), does not look suspicious (I think):
# ls -pal /usr/lib/llvm/17/lib/libclang.so.17 /usr/lib/llvm/17/lib/libclang.so.17.0.6
lrwxrwxrwx 1 root root       18 Jun 25 17:39 /usr/lib/llvm/17/lib/libclang.so.17 -> libclang.so.17.0.6
-rwxr-xr-x 1 root root 14893056 Jun 25 17:39 /usr/lib/llvm/17/lib/libclang.so.17.0.6

The system runs fine (as far as I ca see) but I am a bit nervous about rebooting at the moment.

Any suggestions?

Regards,
-- 
Dan Johansson,
***************************************************
This message is printed on 100% recycled electrons!
***************************************************

Re: [gentoo-user] ldconfig segfaults after updating to 23.0 profil

[Michael]

[-- Attachment #1: Type: text/plain, Size: 1976 bytes --]

On Thursday, 27 June 2024 20:11:51 BST Dan Johansson wrote:
> Hello,
> 
> After updating my system to a 23.0 profile,
> default/linux/amd64/23.0/split-usr/desktop/plasma (stable), ldconfig has
> started segfaulting.

The 23.0 profile uses merged /usr as its default.  You can, however, remain 
with a split /usr for now.  What you can't do is mix the two.


> Here are the last few lines of "strace ldconfig":
> newfstatat(AT_FDCWD,
> "/usr/lib/rust/lib/librustc_driver-131b866216b2910c.so",
> {st_mode=S_IFREG|0644, st_size=153456592, ...}, 0) = 0 openat(AT_FDCWD,
> "/usr/lib/llvm/17/lib", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3
> fstat(3, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
> getdents64(3, 0x5555572629d0 /* 22 entries */, 32768) = 824
> newfstatat(AT_FDCWD, "/usr/lib/llvm/17/lib/libclang.so.17",
> {st_mode=S_IFREG|0755, st_size=17506304, ...}, 0) = 0 openat(AT_FDCWD,
> "/usr/lib/llvm/17/lib/libclang.so.17", O_RDONLY) = 4 fstat(4,
> {st_mode=S_IFREG|0755, st_size=17506304, ...}) = 0
> mmap(NULL, 17506304, PROT_READ, MAP_SHARED, 4, 0) = 0x7fb6eb2d3000
> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x7fb6ed37c4dc}
> --- +++ killed by SIGSEGV +++
> Segmentation fault
> 
> The file in question (I think), does not look suspicious (I think):
> # ls -pal /usr/lib/llvm/17/lib/libclang.so.17
> /usr/lib/llvm/17/lib/libclang.so.17.0.6 lrwxrwxrwx 1 root root       18 Jun
> 25 17:39 /usr/lib/llvm/17/lib/libclang.so.17 -> libclang.so.17.0.6
> -rwxr-xr-x 1 root root 14893056 Jun 25 17:39
> /usr/lib/llvm/17/lib/libclang.so.17.0.6
> 
> The system runs fine (as far as I ca see) but I am a bit nervous about
> rebooting at the moment.
> 
> Any suggestions?

I run a merged /usr profile 23.0, and my libclang.so.17.0.6 is bigger:

# ls -la /usr/lib/llvm/17/lib64/libclang.so.17.0.6 
-rwxr-xr-x 1 root root 32579024 Jun  2 12:15 /usr/lib/llvm/17/lib64/
libclang.so.17.0.6

Have you re-emerged your toolchain and in particular sys-libs/glibc?

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] ldconfig segfaults after updating to 23.0 profil

[Dan Johansson]

On 27.06.24 21:37, Michael wrote:
> On Thursday, 27 June 2024 20:11:51 BST Dan Johansson wrote:
>> Hello,
>>
>> After updating my system to a 23.0 profile,
>> default/linux/amd64/23.0/split-usr/desktop/plasma (stable), ldconfig has
>> started segfaulting.
> 
> The 23.0 profile uses merged /usr as its default.  You can, however, remain
> with a split /usr for now.  What you can't do is mix the two.
> 
> 
>> Here are the last few lines of "strace ldconfig":
>> newfstatat(AT_FDCWD,
>> "/usr/lib/rust/lib/librustc_driver-131b866216b2910c.so",
>> {st_mode=S_IFREG|0644, st_size=153456592, ...}, 0) = 0 openat(AT_FDCWD,
>> "/usr/lib/llvm/17/lib", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3
>> fstat(3, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
>> getdents64(3, 0x5555572629d0 /* 22 entries */, 32768) = 824
>> newfstatat(AT_FDCWD, "/usr/lib/llvm/17/lib/libclang.so.17",
>> {st_mode=S_IFREG|0755, st_size=17506304, ...}, 0) = 0 openat(AT_FDCWD,
>> "/usr/lib/llvm/17/lib/libclang.so.17", O_RDONLY) = 4 fstat(4,
>> {st_mode=S_IFREG|0755, st_size=17506304, ...}) = 0
>> mmap(NULL, 17506304, PROT_READ, MAP_SHARED, 4, 0) = 0x7fb6eb2d3000
>> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x7fb6ed37c4dc}
>> --- +++ killed by SIGSEGV +++
>> Segmentation fault
>>
>> The file in question (I think), does not look suspicious (I think):
>> # ls -pal /usr/lib/llvm/17/lib/libclang.so.17
>> /usr/lib/llvm/17/lib/libclang.so.17.0.6 lrwxrwxrwx 1 root root       18 Jun
>> 25 17:39 /usr/lib/llvm/17/lib/libclang.so.17 -> libclang.so.17.0.6
>> -rwxr-xr-x 1 root root 14893056 Jun 25 17:39
>> /usr/lib/llvm/17/lib/libclang.so.17.0.6
>>
>> The system runs fine (as far as I ca see) but I am a bit nervous about
>> rebooting at the moment.
>>
>> Any suggestions?
> 
> I run a merged /usr profile 23.0, and my libclang.so.17.0.6 is bigger:
> 
> # ls -la /usr/lib/llvm/17/lib64/libclang.so.17.0.6
> -rwxr-xr-x 1 root root 32579024 Jun  2 12:15 /usr/lib/llvm/17/lib64/
> libclang.so.17.0.6
> 
> Have you re-emerged your toolchain and in particular sys-libs/glibc?

Found the culprit. It was sys-devel/clang

scanelf: /usr/lib/llvm/17/bin/clang-tidy: Invalid section header info (2)
scanelf: /usr/lib/llvm/17/bin/c-index-test: Invalid section header info (2)
scanelf: /usr/lib/llvm/17/lib/libclang.so: Invalid section header info (2)
scanelf: /usr/lib/llvm/17/lib/libclang.so.17: Invalid section header info (2)
scanelf: /usr/lib/llvm/17/lib/libclang.so.17.0.6: Invalid section header info (2)

After re-emerging sys-devel/clang again, ldconfig does not throw a sigsev.
-- 
Dan Johansson
***************************************************
This message is printed on 100% recycled electrons!
***************************************************

Re: [gentoo-user] ldconfig segfaults after updating to 23.0 profil

[Michael]

[-- Attachment #1: Type: text/plain, Size: 2820 bytes --]

On Tuesday, 2 July 2024 20:05:37 BST Dan Johansson wrote:
> On 27.06.24 21:37, Michael wrote:
> > On Thursday, 27 June 2024 20:11:51 BST Dan Johansson wrote:
> >> Hello,
> >> 
> >> After updating my system to a 23.0 profile,
> >> default/linux/amd64/23.0/split-usr/desktop/plasma (stable), ldconfig has
> >> started segfaulting.
> > 
> > The 23.0 profile uses merged /usr as its default.  You can, however,
> > remain
> > with a split /usr for now.  What you can't do is mix the two.
> > 
> >> Here are the last few lines of "strace ldconfig":
> >> newfstatat(AT_FDCWD,
> >> "/usr/lib/rust/lib/librustc_driver-131b866216b2910c.so",
> >> {st_mode=S_IFREG|0644, st_size=153456592, ...}, 0) = 0 openat(AT_FDCWD,
> >> "/usr/lib/llvm/17/lib", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3
> >> fstat(3, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
> >> getdents64(3, 0x5555572629d0 /* 22 entries */, 32768) = 824
> >> newfstatat(AT_FDCWD, "/usr/lib/llvm/17/lib/libclang.so.17",
> >> {st_mode=S_IFREG|0755, st_size=17506304, ...}, 0) = 0 openat(AT_FDCWD,
> >> "/usr/lib/llvm/17/lib/libclang.so.17", O_RDONLY) = 4 fstat(4,
> >> {st_mode=S_IFREG|0755, st_size=17506304, ...}) = 0
> >> mmap(NULL, 17506304, PROT_READ, MAP_SHARED, 4, 0) = 0x7fb6eb2d3000
> >> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR,
> >> si_addr=0x7fb6ed37c4dc}
> >> --- +++ killed by SIGSEGV +++
> >> Segmentation fault
> >> 
> >> The file in question (I think), does not look suspicious (I think):
> >> # ls -pal /usr/lib/llvm/17/lib/libclang.so.17
> >> /usr/lib/llvm/17/lib/libclang.so.17.0.6 lrwxrwxrwx 1 root root       18
> >> Jun
> >> 25 17:39 /usr/lib/llvm/17/lib/libclang.so.17 -> libclang.so.17.0.6
> >> -rwxr-xr-x 1 root root 14893056 Jun 25 17:39
> >> /usr/lib/llvm/17/lib/libclang.so.17.0.6
> >> 
> >> The system runs fine (as far as I ca see) but I am a bit nervous about
> >> rebooting at the moment.
> >> 
> >> Any suggestions?
> > 
> > I run a merged /usr profile 23.0, and my libclang.so.17.0.6 is bigger:
> > 
> > # ls -la /usr/lib/llvm/17/lib64/libclang.so.17.0.6
> > -rwxr-xr-x 1 root root 32579024 Jun  2 12:15 /usr/lib/llvm/17/lib64/
> > libclang.so.17.0.6
> > 
> > Have you re-emerged your toolchain and in particular sys-libs/glibc?
> 
> Found the culprit. It was sys-devel/clang
> 
> scanelf: /usr/lib/llvm/17/bin/clang-tidy: Invalid section header info (2)
> scanelf: /usr/lib/llvm/17/bin/c-index-test: Invalid section header info (2)
> scanelf: /usr/lib/llvm/17/lib/libclang.so: Invalid section header info (2)
> scanelf: /usr/lib/llvm/17/lib/libclang.so.17: Invalid section header info
> (2) scanelf: /usr/lib/llvm/17/lib/libclang.so.17.0.6: Invalid section
> header info (2)
> 
> After re-emerging sys-devel/clang again, ldconfig does not throw a sigsev.

How did you discover this?  Was it higher up in the build log?

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] ldconfig segfaults after updating to 23.0 profil

[Dan Johansson]

On 02.07.24 21:16, Michael wrote:
> On Tuesday, 2 July 2024 20:05:37 BST Dan Johansson wrote:
>> On 27.06.24 21:37, Michael wrote:
>>> On Thursday, 27 June 2024 20:11:51 BST Dan Johansson wrote:
>>>> Hello,
>>>>
>>>> After updating my system to a 23.0 profile,
>>>> default/linux/amd64/23.0/split-usr/desktop/plasma (stable), ldconfig has
>>>> started segfaulting.
>>>
>>> The 23.0 profile uses merged /usr as its default.  You can, however,
>>> remain
>>> with a split /usr for now.  What you can't do is mix the two.
>>>
>>>> Here are the last few lines of "strace ldconfig":
>>>> newfstatat(AT_FDCWD,
>>>> "/usr/lib/rust/lib/librustc_driver-131b866216b2910c.so",
>>>> {st_mode=S_IFREG|0644, st_size=153456592, ...}, 0) = 0 openat(AT_FDCWD,
>>>> "/usr/lib/llvm/17/lib", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3
>>>> fstat(3, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
>>>> getdents64(3, 0x5555572629d0 /* 22 entries */, 32768) = 824
>>>> newfstatat(AT_FDCWD, "/usr/lib/llvm/17/lib/libclang.so.17",
>>>> {st_mode=S_IFREG|0755, st_size=17506304, ...}, 0) = 0 openat(AT_FDCWD,
>>>> "/usr/lib/llvm/17/lib/libclang.so.17", O_RDONLY) = 4 fstat(4,
>>>> {st_mode=S_IFREG|0755, st_size=17506304, ...}) = 0
>>>> mmap(NULL, 17506304, PROT_READ, MAP_SHARED, 4, 0) = 0x7fb6eb2d3000
>>>> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR,
>>>> si_addr=0x7fb6ed37c4dc}
>>>> --- +++ killed by SIGSEGV +++
>>>> Segmentation fault
>>>>
>>>> The file in question (I think), does not look suspicious (I think):
>>>> # ls -pal /usr/lib/llvm/17/lib/libclang.so.17
>>>> /usr/lib/llvm/17/lib/libclang.so.17.0.6 lrwxrwxrwx 1 root root       18
>>>> Jun
>>>> 25 17:39 /usr/lib/llvm/17/lib/libclang.so.17 -> libclang.so.17.0.6
>>>> -rwxr-xr-x 1 root root 14893056 Jun 25 17:39
>>>> /usr/lib/llvm/17/lib/libclang.so.17.0.6
>>>>
>>>> The system runs fine (as far as I ca see) but I am a bit nervous about
>>>> rebooting at the moment.
>>>>
>>>> Any suggestions?
>>>
>>> I run a merged /usr profile 23.0, and my libclang.so.17.0.6 is bigger:
>>>
>>> # ls -la /usr/lib/llvm/17/lib64/libclang.so.17.0.6
>>> -rwxr-xr-x 1 root root 32579024 Jun  2 12:15 /usr/lib/llvm/17/lib64/
>>> libclang.so.17.0.6
>>>
>>> Have you re-emerged your toolchain and in particular sys-libs/glibc?
>>
>> Found the culprit. It was sys-devel/clang
>>
>> scanelf: /usr/lib/llvm/17/bin/clang-tidy: Invalid section header info (2)
>> scanelf: /usr/lib/llvm/17/bin/c-index-test: Invalid section header info (2)
>> scanelf: /usr/lib/llvm/17/lib/libclang.so: Invalid section header info (2)
>> scanelf: /usr/lib/llvm/17/lib/libclang.so.17: Invalid section header info
>> (2) scanelf: /usr/lib/llvm/17/lib/libclang.so.17.0.6: Invalid section
>> header info (2)
>>
>> After re-emerging sys-devel/clang again, ldconfig does not throw a sigsev.
> 
> How did you discover this?  Was it higher up in the build log?

No, that was while I was "hunting" another issue and run perl-cleaner, then the scanelf lines showed up in the output.
Stange thing is that I did run "emerge --emptytree @world" atleast two times before that.
But now it seems OK and I am happy.

-- 
Dan Johansson
***************************************************
This message is printed on 100% recycled electrons!
***************************************************

Re: [gentoo-user] ldconfig segfaults after updating to 23.0 profil

[Waldo Lemmer]

[-- Attachment #1: Type: text/plain, Size: 2089 bytes --]

FYI, Gmail sees this email as spam:

> Be careful with this message
>
> The sender hasn't authenticated this message so Gmail can't verify that
it actually came from them. Avoid clicking links, downloading attachments,
or replying with personal information.

On Thu, Jun 27, 2024 at 9:12 PM Dan Johansson <Dan.Johansson@dmj.nu> wrote:

> Hello,
>
> After updating my system to a 23.0 profile,
> default/linux/amd64/23.0/split-usr/desktop/plasma (stable), ldconfig has
> started segfaulting.
>
> Here are the last few lines of "strace ldconfig":
> newfstatat(AT_FDCWD,
> "/usr/lib/rust/lib/librustc_driver-131b866216b2910c.so",
> {st_mode=S_IFREG|0644, st_size=153456592, ...}, 0) = 0
> openat(AT_FDCWD, "/usr/lib/llvm/17/lib",
> O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3
> fstat(3, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
> getdents64(3, 0x5555572629d0 /* 22 entries */, 32768) = 824
> newfstatat(AT_FDCWD, "/usr/lib/llvm/17/lib/libclang.so.17",
> {st_mode=S_IFREG|0755, st_size=17506304, ...}, 0) = 0
> openat(AT_FDCWD, "/usr/lib/llvm/17/lib/libclang.so.17", O_RDONLY) = 4
> fstat(4, {st_mode=S_IFREG|0755, st_size=17506304, ...}) = 0
> mmap(NULL, 17506304, PROT_READ, MAP_SHARED, 4, 0) = 0x7fb6eb2d3000
> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR,
> si_addr=0x7fb6ed37c4dc} ---
> +++ killed by SIGSEGV +++
> Segmentation fault
>
> The file in question (I think), does not look suspicious (I think):
> # ls -pal /usr/lib/llvm/17/lib/libclang.so.17
> /usr/lib/llvm/17/lib/libclang.so.17.0.6
> lrwxrwxrwx 1 root root       18 Jun 25 17:39
> /usr/lib/llvm/17/lib/libclang.so.17 -> libclang.so.17.0.6
> -rwxr-xr-x 1 root root 14893056 Jun 25 17:39
> /usr/lib/llvm/17/lib/libclang.so.17.0.6
>
> The system runs fine (as far as I ca see) but I am a bit nervous about
> rebooting at the moment.
>
> Any suggestions?
>
> Regards,
> --
> Dan Johansson,
> ***************************************************
> This message is printed on 100% recycled electrons!
> ***************************************************
>
>

[-- Attachment #2: Type: text/html, Size: 2512 bytes --]