You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presumably because the ubuntu-latest runners have stepped forward (as with #575), the powerpc64el cross-build and -run test is failing an apparently random subset of the tests. I am unable to reproduce these crashes on my Power machine, so I am inclined to think it's an artifact of emulation. With a little elbow grease and prodding, I can reproduce it on WSL2. It looks like we aren't making it very far into program startup... with qemu tracing its heart out (and some judicious editing of the resulting 60MB log), we see that the signal is
Bisection points at this being the fault of qemu/qemu@4dcf078 . The first release to contain that commit was v5.0.0, putting it after Ununtu Focal and before Impish (and so Jammy). I don't understand why that change would trigger this behavior, but so it goes.
For history, I used this somewhat awkward command to build, since qemu has changed their build system and output layout a few times in the large span between v4.2.1 and today:
(rm -rf _build; mkdir _build; cd _build; ../configure --target-list=ppc64le-linux-user --disable-werror --disable-docs; ninja || make -j5; ln -s ppc64le-linux-user/qemu-ppc64le .)
Presumably because the ubuntu-latest runners have stepped forward (as with #575), the powerpc64el cross-build and -run test is failing an apparently random subset of the tests. I am unable to reproduce these crashes on my Power machine, so I am inclined to think it's an artifact of emulation. With a little elbow grease and prodding, I can reproduce it on WSL2. It looks like we aren't making it very far into program startup... with qemu tracing its heart out (and some judicious editing of the resulting 60MB log), we see that the signal is
and the program counter is presumably near the last TB we entered, which was
si_code=1
isSEGV_MAPERR
("address not mapped to object").The fault address
0x4001be5000
is within the dynamic linker's load oflibsdtdc++
and is not in the range of any subsequent
mprotect
call. The PC0x4001e2f724
is withinlibc
:That trace certainly suggests that there should be memory at 0x4001be5000, I think.
qemu
v4.2.1
, approximately what shipped in Ubuntu Focal, lets the test pass. I'll bisectqemu
and report back.The text was updated successfully, but these errors were encountered: