From 400a601edda2ad5d160bdbe792365d08454905f1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ciro=20Santilli=20=E5=85=AD=E5=9B=9B=E4=BA=8B=E4=BB=B6=20?= =?UTF-8?q?=E6=B3=95=E8=BD=AE=E5=8A=9F?= Date: Mon, 18 Feb 2019 00:00:01 +0000 Subject: [PATCH] qemu user: stack smashing detected find precise bug report --- README.adoc | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/README.adoc b/README.adoc index d266ab7..488219d 100644 --- a/README.adoc +++ b/README.adoc @@ -3142,6 +3142,8 @@ The ID is just hardcoded on the source: ===== stack smashing detected +Bug report and workaround: https://bugs.launchpad.net/qemu/+bug/1701798/comments/16 + Reproduction: .... @@ -3165,11 +3167,15 @@ The following all work however: A non-QEMU example of stack smashing is shown at: https://stackoverflow.com/questions/1345670/stack-smashing-detected/51897264#51897264 -Related bug reports: +I've also tested on an Ubuntu 16.04 guest and the failure is different one: -* https://bugs.launchpad.net/qemu/+bug/1701808 -* https://bugs.launchpad.net/qemu/+bug/1776478 -* https://github.com/multiarch/ubuntu-debootstrap/issues/10 +.... +qemu: uncaught target signal 4 (Illegal instruction) - core dumped +.... + +So my theory is that it must be picking up something from the host as described at: https://bugs.launchpad.net/qemu/+bug/1701798 since there are different errors in different hosts. + +This is also consistent with the fact that aarch64 worked: those binaries are not present for QEMU to get confused in that case. Tested at: 2e32389ebf1bedd89c682aa7b8fe42c3c0cf96e5 + 1.