3rd-party/linux-kernel-module-cheat
1
0
Fork 0
mirror of https://github.com/cirosantilli/linux-kernel-module-cheat.git synced 2026-01-25 11:11:35 +01:00
Code Issues Releases Wiki Activity

qemu user: stack smashing detected find precise bug report

Browse Source
This commit is contained in:
Ciro Santilli 六四事件 法轮功
2019-02-18 00:00:01 +00:00
parent 48778ccd9c
commit 400a601edd
1 changed files with 10 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
README.adoc
View File

@@ -3142,6 +3142,8 @@ The ID is just hardcoded on the source:
===== stack smashing detected ===== stack smashing detected
Bug report and workaround: https://bugs.launchpad.net/qemu/+bug/1701798/comments/16
Reproduction: 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 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 qemu: uncaught target signal 4 (Illegal instruction) - core dumped
* https://github.com/multiarch/ubuntu-debootstrap/issues/10 ....
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. Tested at: 2e32389ebf1bedd89c682aa7b8fe42c3c0cf96e5 + 1.