Take the tour ×  What set of GCC options provide the best
protection against memory corruption vulnerabilities such as
Buffer Overflows, and Dangling Pointers? Does GCC provide any
type of ROP chain mitigation? Are there performance concerns or
other issues that would prevent this GCC option from being on a
mission critical application?  I am looking at the Debian
Hardening Guide as well as GCC Mudflap. Here are the following
configurations I am considering:  -fstack-protector --param ssp-
buffer-size=4 -fPIE -pie -Wl,-z,relro,-z,now (ld -z relro and ld
-z now)  Are there any improvments that can be made to this set
of options?  We are most worried about protecting WebKit form
attacks.  share|improve this question gcc -x ada. Seriously, if
you don't want exploitable programs, start by using a
programming language that doesn't go out of its way to let
programmers write exploitable code. –  Gilles Nov 25 '12 at
19:28 @Gilles cool let me know when they write a browser in ada.
–  Rook Nov 25 '12 at 19:38 There was