Did we open a precise glibc upstream bug for this so I can go upvote it? :-)
Workaround from #12 also worked for me.
Tested on Buildroot with this precise setup: https://github.com/cirosantilli/linux-kernel-module-cheat/tree/e855a262fd872171156894e9045814cb0f346dab#stack-smashing-detected
For Google, the error message in that setup is:
*** stack smashing detected ***: <unknown> terminated qemu: uncaught target signal 6 (Aborted) - core dumped
but must be the same as reported here just with a different glibc setup leading to slightly different crash.
Did we open a precise glibc upstream bug for this so I can go upvote it? :-)
Workaround from #12 also worked for me.
Tested on Buildroot with this precise setup: https:/ /github. com/cirosantill i/linux- kernel- module- cheat/tree/ e855a262fd87217 1156894e9045814 cb0f346dab# stack-smashing- detected
For Google, the error message in that setup is:
*** stack smashing detected ***: <unknown> terminated
qemu: uncaught target signal 6 (Aborted) - core dumped
but must be the same as reported here just with a different glibc setup leading to slightly different crash.