| 2015-10-25 06:22:14 |
Steven Stallion |
description |
Due to a latent bug in a Makefile, source had been compiling with -fstack-protector-strong since the 4.9 release, however the flag was not being passed to the linker. For example:
arm-none-eabi-gcc -o foo.o -fstack-protector-strong -c foo.c
When this bug was corrected, ld begin failing as it could not find libssp/libssp_nonshared:
../arm-none-eabi/bin/ld: cannot find -lssp_nonshared
../arm-none-eabi/bin/ld: cannot find -lssp
collect2: error: ld returned 1 exit status
This would seem to indicate that arm-none-eabi-gcc does not support stack protection. Is this the case? Is it expected that compiling with -fstack-protector-strong when libssp is not present fails silently? Is it possible to add support for stack protection in the next release? |
Due to a latent bug in a Makefile, source had been compiling with -fstack-protector-strong since the 4.9 release, however the flag was not being passed to the linker. For example:
arm-none-eabi-gcc -o foo.o -fstack-protector-strong -c foo.c
When this bug was corrected, ld begin failing as it could not find libssp/libssp_nonshared:
arm-none-eabi-gcc -o foo.elf -fstack-protector-strong foo.c
../arm-none-eabi/bin/ld: cannot find -lssp_nonshared
../arm-none-eabi/bin/ld: cannot find -lssp
collect2: error: ld returned 1 exit status
This would seem to indicate that arm-none-eabi-gcc does not support stack protection. Is this the case? Is it expected that compiling with -fstack-protector-strong when libssp is not present fails silently? Is it possible to add support for stack protection in the next release? |
|
