Closed fcambus closed 4 years ago
It took a bit of fiddling to find a way to trigger this fault on test20, but managed to do that with:
./configure CFLAGS="-fstack-protector --param ssp-buffer-size=4 -g -O0"
Appears I introduced a bug after "Allow Spiros to be scaled and/or shifted. Scaling bug fixed."
Valgrind comes clean for all tests here:
./libtool --mode=execute valgrind -v --error-exitcode=1 ./tests/call-test15
At this point "Corrected directions of '[' and ']' for drawing example 'a'" valgrind begins showing problems for test 0,7,9,14,15
Hi @fcambus - appears the git comment auto closed this issue, I'll reopen it.
Would you mind giving the latest patch a spin? Fix memory access bug/error created earlier by patch 2017-10-28
There is one more thing that has my attention that I'd like to stomp-out before doing a fresh release.
Thanks, Joe
Thanks for looking into this issue.
I can confirm the test suite now runs all the tests correctly with your latest patch.
Hi,
The issue can be reproduced out of the box when building and running the test suite on OpenBSD and FreeBSD.
It can be reproduced on Linux with GCC by enabling the Stack Smashing Protector (SSP):