This was a problem when building glibc with -ftree-vectorize
I have the exact same error, same OS.
I don't understand your comments. since you are using STEAM_RUNTIME=1 (which I guess equates to the steamruntime USE flag being enabled in steam-launcher), this means that steam will use the libc it comes with, not the one compiled by gentoo.
so surely the kernel trap refers to valve's libc, not the system one. which would mean that changing the CFLAGS on the system libc would have no effect on this bug whatsoever. what am I missing?
plus my make.conf CFLAGS="-O2 -pipe" don't even enable '-ftree-vectorize' which only comes in with -O3.
how can someone debug this reaper process? it's got no debug symbols, no sources afaict, plus steam re-syncs the reaper binary on start if it detects it's been changed.
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
I've been using STEAM_RUNTIME=1 for a while without any issues but suddenly no games will start. I am not seeing any obvious error messages in the console but I am seeing a glibc segfault in dmesg.
I am using sys-libs/glibc-2.34-r2 which I believe was recently updated and is probably what is causing the issue here. If you have any suggestions for debugging this further, please let me know. I am not even sure how I can attach gdb to the game that is being launched.
Steps for reproducing this issue: