/usr/share/doc/gcc-9-base
NameSizeModeActions
fortran/-0755rm
gcc/-0755rm
gomp/-0755rm
itm/-0755rm
quadmath/-0755rm
sanitizer/-0755rm
changelog.Debian.gz1840990644editdlrm
changelog.gz1610670644editdlrm
copyright752850644editdlrm
NEWS.gz151730644editdlrm
NEWS.html655080644editdlrm
README.Bugs111560644editdlrm
README.Debian.amd64.gz38470644editdlrm
README.ssp11650644editdlrm
TODO.Debian16530644editdlrm
Edit: /usr/share/doc/gcc-9-base/README.ssp (1165B)
Stack smashing protection is a feature of GCC that enables a program to detect buffer overflows and immediately terminate execution, rather than continuing execution with corrupt internal data structures. It uses "canaries" and local variable reordering to reduce the likelihood of stack corruption through buffer overflows. Options that affect stack smashing protection: -fstack-protector Enables protection for functions that are vulnerable to stack smashing, such as those that call alloca() or use pointers. -fstack-protector-all Enables protection for all functions. -Wstack-protector Warns about functions that will not be protected. Only active when -fstack-protector has been used. Applications built with stack smashing protection should link with the ssp library by using the option "-lssp" for systems with glibc-2.3.x or older; glibc-2.4 and newer versions provide this functionality in libc. The Debian architectures alpha, hppa, ia64, m68k, mips, mipsel do not have support for stack smashing protection. More documentation can be found at the project's website: http://researchweb.watson.ibm.com/trl/projects/security/ssp/