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! ***************************************************

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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?

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmZ9v24ACgkQseqq9sKV Zxn56RAAzRMb549CqKTLmHB/gnLThjltU17Jxi9ekX9wPL724LYTpHVTEoTxDlBq pH9FM1soR5fAc4VJUh6qeQAIrun2v9VvMAgkiRGKv6J3YPoUc3c8hp8zvCIl1POu 66ISVWd9stn0BAyCn0H9RtspjRb9UZaM/0+p+5bvgMV7Zf3OIiYmpjSE4mKyL3f9 x1xCZ3OEIb4EfuhLqcewq6FtQYEE17oAUOr9GAhWIPan5Q+Ntr8DBvCm5aUTT9Jz h8LPniFUqz3RrNHvK0tH1Ii/bnIAwGRc0krf7SB1K+BypaPOr9+TdDdp4HwElpA8 NCznMK9FUuC/FBqiphKqM7TjXRfCfdmN+0VaIKEpC7FcdtXMEwSgKb7dnJAivdNL QnfQx46JusNoQUxduEnFFw4uHSJxOZ7ZIrpEj9wssIJdYvJ8JSNO1JRfkduvdzKu Nqnbmj10UIQCwZeVs4E0/t9IjmePSDtABV/mwxrHFLsQMFR8C+kMoO/2PbYDDDRo TXL9Br8ZQ4s8Hs03YwNIyKgLjofwXnA7KHO2rd9zasdJh9KW+0f8cSciL9gF9MDC QPSLVIEpxISHrH3mbdqzHwOC23KBsrheIkRsMzgf/4h3fTk7jNdQEfZCE9ht/txN PveAymQ4UiLHSzN5Zw1R+2RCShapoUIkvrTcdilX6H2eAajm6N8=
=cawI
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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! ***************************************************

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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?

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmaEUgYACgkQseqq9sKV ZxkDvw/7BJ2W0Nz2fXSF2pr95xbTdO5yHRtGX6RGS8ASGgeTuSuKyTNkr32GMcsj wt2yOdeZd0A89VP7RC8gcbs3d1oDsQWjGkqrozz2iT9jilzhcGEfZAbRPfjKNlg/ X7pE12pYuTLlTEErg5LQ9cK8oZlKTUALRO5H2E67l07plYFabpDCFYJszmhWOjLj s7npr3ItPSWCEZNPovCm408l8gQIJmIf206Hv5GIlNMwoxGxPD0SlAqe6aPSiFl5 ycMACKVFlA17o4bbGUL6veb4NcOaz2gEVsUOo2q0dV1OlrvvgVepLlNNIPR4T9dx nZ90d+hWSydWo0NbZeLk67D4brYIOVYmTlsGvI2AUmRi44i76Nq0WFcm6jtQoW9K WAN30/1yN2saz7VD1cVjlXLsFyXm0D/DWpddYfx2y9uZBfoPK9CClF3gyaEUE2c1 //eYEOMAom/kOxJmqbg+AOd+o0IsK41o7uQOCKfIcDl2PRU1ov7LM1VGJk++RgW2 297URKlZmG6I4wuCq/GTkaiBXr0oFBLVOJjs7ASkJT4uAMd6i+tqyM983+w9KSkB QVisakPIDseuBEC0IatMTCcNMpY6w1TW0FtFYELmPELWuGoQKogP2AmfRXmn7fL/ Nf1posZ17tGbFuXOegwAfEsHIUmUFEY21V8jBRY9l4UMEqiQA/Y=
=+AXi
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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! ***************************************************

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)