Your message dated Fri, 8 Aug 2025 09:54:29 +0300 with message-id <[email protected]> and subject line Re: #999421: still happens in 8.0.2+dfsg-3 has caused the Debian Bug report #999421, regarding qemu-user-static: lli-15/arm64 causes segfault on amd64 host to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 999421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999421 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: qemu-user-static Version: 1:6.1+dfsg-8 Severity: important on an amd64 host in in arm64 chroot running under qemu-user-static, I observed some segmentation fault while building pocl against llvm-13 this is not reproducible on a porter box it works fine with lli-12 in the arm64 chroot llvm-13 and clang-13 need to be installed # cat compile_test_6cqj4.c #ifndef offsetof #define offsetof(type, member) ((char *) &((type *) 0)->member - (char *) 0) #endif typedef double double16 __attribute__((__ext_vector_type__(16))); int main(int argc, char** argv) { typedef struct { char x; double16 y; } ac__type_alignof_; int r = offsetof(ac__type_alignof_, y); return r; } # clang-13 -o try_run.bc -x c -emit-llvm -c --target=aarch64-unknown-linux-gnu compile_test_6cqj4.c # lli-13 -force-interpreter try_run.bc ; echo $? PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace. Stack dump: 0. Program arguments: lli-13 -force-interpreter try_run.bc Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it): /usr/lib/aarch64-linux-gnu/libLLVM-13.so.1(_ZN4llvm3sys15PrintStackTraceERNS_11raw_ostreamEi+0x44)[0x55015f4368] /usr/lib/aarch64-linux-gnu/libLLVM-13.so.1(_ZN4llvm3sys17RunSignalHandlersEv+0x70)[0x55015f2588] /usr/lib/aarch64-linux-gnu/libLLVM-13.so.1(+0xdb9914)[0x55015f4914] [0x4dc890] [0x5509ac000c] /usr/lib/aarch64-linux-gnu/libLLVM-13.so.1(+0x22cd730)[0x5502b08730] lli-13(_Z9runOrcJITPKc+0x2218)[0x41aa20] lli-13(main+0x290)[0x416960] /lib/aarch64-linux-gnu/libc.so.6(__libc_start_main+0xe8)[0x55063ea8b8] lli-13(_start+0x38)[0x415278] qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault 139 Andreas
--- End Message ---
--- Begin Message ---Version: 1:9.0.0+dfsg-1 This issue has been fixed by the upstream during qemu 9.0 development cycle. Especially, one of the following upstream commits fixed it: https://gitlab.com/qemu-project/qemu/-/commit/2952b642a555207748dd961fcbfdc48f198eebb6 https://gitlab.com/qemu-project/qemu/-/commit/3bfa271e46b506b2ceff41e3b258ad2ddeb25bc3 https://gitlab.com/qemu-project/qemu/-/commit/ad87d26e6bb13257409f412224c862fc54025e8b https://gitlab.com/qemu-project/qemu/-/commit/68098de90e653adbb8bfc30f85aab9d12f111b80 In particular, the reproducer works (ie, does not reproduce) in trixie version of qemu (10.0). Closing this bug report now, finally. Thanks, /mjt
--- End Message ---
