Bug#1081849: qemu-i386: can't run busybox:i386 on ppc64el: Segmentation fault
Simon McVittie <[email protected]>
| Newsgroups | gmane.linux.debian.ports.powerpc |
|---|---|
| Message-ID | <Zub2B8XBl45TI1BY__43358.4236701549$1726412428$gmane$org@remnant.pseudorandom.co.uk> |
Package: qemu-user Version: 1:9.0.2+ds-2+b1 Severity: normal User: [email protected] Usertags: ppc64el X-Debbugs-Cc: [email protected] The new cross-exe-wrapper package in src:architecture-properties runs binaries from a foreign architecture, either directly or via qemu-user. Its autopkgtest uses busybox from each release architecture (specifically the `busybox true` and `busybox echo` applets) as a smoke-test to see whether this works as intended. On ppc64el, the result indicates that the qemu-i386 in qemu-user:ppc64el can't run busybox:i386: > 137s qemu: uncaught target signal 11 (Segmentation fault) - core dumped I don't know whether this is specific to busybox, or whether the qemu-i386 in qemu-user:ppc64el doesn't work more generally. architecture-properties (>= 0.2.2) works around this by skipping its self-test on architecture pairs where qemu-$arch doesn't run successfully. smcv