On 1/4/21 4:01 PM, Peter Maydell wrote: > On Mon, 4 Jan 2021 at 13:59, Philippe Mathieu-Daudé <f4...@amsat.org> wrote: >> I don't have access to OSX host. I'll see to install an aarch32 chroot and >> keep testing (not sure what can differ from an i386 guest). >> If I can't find anything I'll resend the same series without the Loongson-3 >> machine, which is the single part adding QOM objects. > > You might also try using valgrind/address-sanitizer/etc, which can > sometimes flag up this kind of bug on x86-64 even if by default > it happens to work.
On 32-bit I hit https://github.com/google/sanitizers/issues/954: $ qemu-system-mips64el AddressSanitizer:DEADLYSIGNAL ================================================================= ==18063==ERROR: AddressSanitizer: SEGV on unknown address 0xb7f20e40 (pc 0xb7f20e54 bp 0xbf86556c sp 0xbf86552c T16777215) ==18063==The signal is caused by a WRITE memory access. #0 0xb7f20e53 (/lib/ld-linux.so.2+0x11e53) #1 0xeb9b59 (/tmp/build/qemu-system-mips64el+0xa86b59) #2 0xe9c1c2 (/tmp/build/qemu-system-mips64el+0xa691c2) #3 0xb7f1e8ea (/lib/ld-linux.so.2+0xf8ea) #4 0xb7f0fcb9 (/lib/ld-linux.so.2+0xcb9) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV (/lib/ld-linux.so.2+0x11e53) ==18063==ABORTING What is funny is Aurelien is mentioned in the GCC BZ =) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84761 What libc do you use? I'll try to downgrade or reinstall an old distrib...