Stuart Henderson <stu.li...@spacehopper.org> wrote: > On 2023-12-27, Ax0n <a...@h-i-r.net> wrote: > > I had been running #1471 since December 5th without issue, and this week > > upgraded to the latest snapshot (#1567) after which some apps such as > > Firefox won't run. They display "msyscall <hex> a8000 error" followed by a > > core dump. dmesg(1) shows a bogus syscall. I did ensure that I had properly > > sysmerged and updated packages.I waited until the next snapshot hit > > mirrors, and verified that this issue persists with build #1572 and fresh > > packages as well. Lenovo X1 Carbon Gen 8. dmesg in body. I can put core > > dumps somewhere if it helps. > > Not sure how much core dumps will help, but if you can try running > the binaries with problems with LD_DEBUG set in the environment (to > anything) and capture output (e.g. using script(1) as it will likely be > copious) that might give clues. > > How are you updating packages / which mirror? Do you have anything left > in /usr/local/{bin,sbin,lib} etc which still reference any libc.so.97? > > Are you doing anything unusual with LD_PRELOAD (e.g. using a socks > wrapper)?
ktrace -di kdump | grep 'NAMI.*/lib' You will see two libc.so That's not good, and our ld.so is going to need to learn to handle this.