__memset_avx2_unaligned_erms suggests that the code takes an optimization path for AVX which fails due to alignment issues. In regard to the recent upload it comes to mind that it now might take other glibc code (static link) which has different alignment constraints than whatever worked before. But then a) glibc should not pick this method (not 100% qemu's fault until we know where/how this path is taken) and b) since all workloads we tried worked we'd need the workload that fails for debugging. It seems it is all about some android cross build check "/usr/bin/qemu-aarch64-static ./conftest" and the PWD often references "android29".
I've checked a few but none crashed, if anyone affected by this could provide steps to reproduce that would help a lot! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914014 Title: /usr/bin/qemu- aarch64-static:11:__memset_avx2_unaligned_erms:memset:zero_bss:load_elf_image:load_elf_binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1914014/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
