Re: problem with i686-w64-mingw32-gcc -fstack-protector-all

2017-10-08 Thread Christian Franke
Lee wrote: + ./ssp.exe testtestx ./doit: line 11: 9128 Illegal instruction ./ssp.exe testtestx + echo -e '\n\n' The *** stack smashing detected *** message from MinGW runtime is only visible if stdio is attached to a Windows console. Yes! But even after re-reading https://github.com/min

Re: problem with i686-w64-mingw32-gcc -fstack-protector-all

2017-10-04 Thread Lee
On 10/4/17, Christian Franke wrote: > Lee wrote: >> Maybe I'm just Doing It Wrong, but >>gcc -fstack-protector-all >> seems to be working correctly & >>i686-w64-mingw32-gcc -fstack-protector-all >> seems to be broken - eg: >> >> $./ssp testtestx >> Illegal instruction >> >> printf's that

Re: problem with i686-w64-mingw32-gcc -fstack-protector-all

2017-10-04 Thread Christian Franke
Lee wrote: Maybe I'm just Doing It Wrong, but gcc -fstack-protector-all seems to be working correctly & i686-w64-mingw32-gcc -fstack-protector-all seems to be broken - eg: $./ssp testtestx Illegal instruction printf's that happen before the stack over-write don't show up & no "*** stack s

problem with i686-w64-mingw32-gcc -fstack-protector-all

2017-10-03 Thread Lee
Maybe I'm just Doing It Wrong, but gcc -fstack-protector-all seems to be working correctly & i686-w64-mingw32-gcc -fstack-protector-all seems to be broken - eg: $./ssp testtestx Illegal instruction printf's that happen before the stack over-write don't show up & no "*** stack smashing detecte