Recently there was an update rolled out to glibc-2.25.

This update will reproducible destroy my machine when installed. It causes all
kinds of programs including systemd to dump core and then will prevent booting
because a lot of service won't come up, including login service.

I tracked the problem down to glibc-2.25.i686 which when installed also causes
zypper to not work anymore...only chance to recover was an earlier image of
system partition.

Then i found out, that there are two glibc-2.25 versions available on the
tumbleweed repository:

glibc-2.25-1.1.i586
and
glibc-2.25-1.1.i686

The i686 version crashes my machine, but the i586 version is working.

Because the earlier installed glibc was glibc-2.24-1.1.i686, it defaulted to
use the i686 type of the new version.

My processor is an Atom N270. To my knowledge this should be i686 compatible.

Because of the immediate crashes and unbootable system afterwards, i could not
get any logs.

A fellow user from the tumbleweed forums analyzed a core dump:


It took some trickery, but I managed to run GDB on a core dump:


Program terminated with signal SIGSEGV, Segmentation fault.
#0 __memchr_sse2 () at ../sysdeps/i386/i686/multiarch/memchr-sse2.S:249
249 ../sysdeps/i386/i686/multiarch/memchr-sse2.S: No such file or directory.