| 1 |
Am Wed, Mar 30, 2022 at 10:14:38AM +0100 schrieb Michael: |
| 2 |
> On Wednesday, 30 March 2022 09:38:41 BST Nikolay Kichukov (oldumnet) wrote: |
| 3 |
> > Hi Jim, |
| 4 |
> > |
| 5 |
> > On Wed, 2022-03-30 at 00:50 -0400, James Cloos wrote: |
| 6 |
> > > Anyone else seeing a multitude of segv in libc on a stable box with |
| 7 |
> > > =sys-libs/glibc-2.34-r10? |
| 8 |
> > > |
| 9 |
> > > not everything dies, but a lot of important stuff does, including |
| 10 |
> > > portage and gdb.... |
| 11 |
> > > |
| 12 |
> > > profile on that box is: |
| 13 |
> > > |
| 14 |
> > > profiles/default/linux/amd64/17.1/no-multilib/hardened |
| 15 |
> > |
| 16 |
> > I am on default/linux/amd64/17.1/desktop and same glibc and I do not |
| 17 |
> > have any SEGVs. |
| 18 |
> |
| 19 |
> |
| 20 |
> Same glibc here on stable systems, no problem. It could be a RAM problem. |
| 21 |
> Re-seat the RAM modules in their sockets and then see if the problem returns. |
| 22 |
|
| 23 |
I also—once in the past-encountered segfaults when building certain large |
| 24 |
packages, in particular gcc, due to a faulty RAM module. memtest86 revealed |
| 25 |
the problem very quickly. |
| 26 |
|
| 27 |
-- |
| 28 |
Grüße | Greetings | Qapla’ |
| 29 |
Please do not share anything from, with or about me on any social network. |
| 30 |
|
| 31 |
I fall asleep early in the evening and get up late in the morning, |
| 32 |
on the other hand I lie awake for hours in the afternoon. |
Archives