Bug#854889: still fails with qemu from buster-backports
Control: notfound -1 qemu/1:5.0-14~bpo10+1 user@phyhost> sudo chroot sid bin/bash ; echo "EXIT $?" *** longjmp causes uninitialized stack frame ***: terminated Not only it is not obvious if you tried the right binary, but this is also definitely a different issue. So unmarking your markings. Thanks, /mjt
Bug#854889: still fails with qemu from buster-backports
29.12.2020 07:23, Matija Nalis wrote: found 854889 qemu/1:5.0-14~bpo10+1 thanks sparc64 bug is still there with qemu-user-static 1:5.0-14~bpo10+1, trying to enter qemu-debootstrap chroot with qemu-sparc64-static: user@phyhost> sudo chroot sid bin/bash ; echo "EXIT $?" *** longjmp causes uninitialized stack frame ***: terminated EXIT 0 Some simple commands run, and then terminate qemu-sparc64-static immediately: user@phyhost> sudo chroot sid bin/dash ; echo "EXIT $?" # arch sparc64 EXIT 0 user@phyhost> sudo chroot sid md5sum /usr/bin/qemu-sparc64-static ; echo "EXIT $?" a335ea29569463a13455746e67abc56c /usr/bin/qemu-sparc64-static Um. Why are you checking qemu-sparc64-static within your chroot? Why do you think this one is used instead of the one in your regular /usr/bin ? /mjt
Bug#854889: still fails with qemu from buster-backports
found 854889 qemu/1:5.0-14~bpo10+1 thanks sparc64 bug is still there with qemu-user-static 1:5.0-14~bpo10+1, trying to enter qemu-debootstrap chroot with qemu-sparc64-static: user@phyhost> sudo chroot sid bin/bash ; echo "EXIT $?" *** longjmp causes uninitialized stack frame ***: terminated EXIT 0 Some simple commands run, and then terminate qemu-sparc64-static immediately: user@phyhost> sudo chroot sid bin/dash ; echo "EXIT $?" # arch sparc64 EXIT 0 user@phyhost> sudo chroot sid md5sum /usr/bin/qemu-sparc64-static ; echo "EXIT $?" a335ea29569463a13455746e67abc56c /usr/bin/qemu-sparc64-static EXIT 0 user@phyhost> -- Opinions above are GNU-copylefted.
