Anyone else seeing a multitude of segv in libc on a stable box with =sys-libs/glibc-2.34-r10?I am on default/linux/amd64/17.1/desktop and same glibc and I do not
not everything dies, but a lot of important stuff does, including
portage and gdb....
profile on that box is:
profiles/default/linux/amd64/17.1/no-multilib/hardened
-JimC
Hi Jim,
On Wed, 2022-03-30 at 00:50 -0400, James Cloos wrote:
Anyone else seeing a multitude of segv in libc on a stable box with =sys-libs/glibc-2.34-r10?
not everything dies, but a lot of important stuff does, including
portage and gdb....
profile on that box is:
profiles/default/linux/amd64/17.1/no-multilib/hardened
I am on default/linux/amd64/17.1/desktop and same glibc and I do not
have any SEGVs.
On Wednesday, 30 March 2022 09:38:41 BST Nikolay Kichukov (oldumnet) wrote:
Hi Jim,
On Wed, 2022-03-30 at 00:50 -0400, James Cloos wrote:
Anyone else seeing a multitude of segv in libc on a stable box with =sys-libs/glibc-2.34-r10?
not everything dies, but a lot of important stuff does, including
portage and gdb....
profile on that box is:
profiles/default/linux/amd64/17.1/no-multilib/hardened
I am on default/linux/amd64/17.1/desktop and same glibc and I do not
have any SEGVs.
Same glibc here on stable systems, no problem. It could be a RAM problem. Re-seat the RAM modules in their sockets and then see if the problem returns.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (0 / 16) |
Uptime: | 163:48:29 |
Calls: | 10,385 |
Calls today: | 2 |
Files: | 14,057 |
Messages: | 6,416,513 |