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?
signature.asc
Description: This is a digitally signed message part.
