https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-embedded/xa-2.3.14 leaves trace of segfault in dmesg. Discovered on: amd64 (internal ref: ci) NOTE: To reproduce this issue: 1) Install the package with FEATURES=test 2) Check dmesg output with: dmesg -T | grep -E '( segfault | traps:| audit:)' This type of report comes from a check that is a bit outside of the tinderbox, that's the reason because build.log was not provided (however in cases like these the build.log doesn't help much) but if you need further help to diagnose this issue feel free to ask. In any case I'm providing what I can see via dmesg.
[Wed Feb 8 09:20:50 2023] xa[16427]: segfault at 0 ip 00007fdefcc308d9 sp 00007ffc644dc988 error 4 in libc.so.6[7fdefcb0e000+148000] [Wed Feb 8 09:20:50 2023] xa[16432]: segfault at 0 ip 00007fceefff68d9 sp 00007ffcb8e6c3c8 error 4 in libc.so.6[7fceefed4000+148000]
Test suite has several expected failures like: # xa should not allow this to happen. if it does, this test is no good. ../../xa -DBUG=1 -o test.o test.s || exit 0 && exit 1 .data test.s:line 6: 1000:Illegal segment error Break after 1 errors So I think this is normal, or either way it's not ignoring errors so I don't think there's anything to fix here (just test suite noise).
(well, it does feel kind of questionable still but well)
