Am Wed, Mar 30, 2022 at 10:14:38AM +0100 schrieb Michael:
> 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.

I also—once in the past-encountered segfaults when building certain large
packages, in particular gcc, due to a faulty RAM module. memtest86 revealed
the problem very quickly.

-- 
Grüße | Greetings | Qapla’
Please do not share anything from, with or about me on any social network.

I fall asleep early in the evening and get up late in the morning,
on the other hand I lie awake for hours in the afternoon.

Attachment: signature.asc
Description: PGP signature

Reply via email to