AuroraMiddleware/glibc
1
0
Fork 0
mirror of https://sourceware.org/git/glibc.git synced 2024-12-25 04:01:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

manual: update AddressSanitizer discussion

Browse Source 
* manual/string.texi (Truncating Strings): Update obsolescent
reference and use the more-generic term “AddressSanitizer”.
Mention fortification, too.  -fcheck-pointer-bounds is no longer
supported.
This commit is contained in:
Paul Eggert 2023-04-08 13:51:26 -07:00
parent f173e27272
commit 54ae6d81c9
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
manual/string.texi
View File

@ -1088,11 +1088,10 @@ name, a truncated name can identify the wrong user.
Although some buffer overruns can be prevented by manually replacing
calls to copying functions with calls to truncation functions, there
are often easier and safer automatic techniques that cause buffer
overruns to reliably terminate a program, such as GCC's
@option{-fcheck-pointer-bounds} and @option{-fsanitize=address}
options. @xref{Debugging Options,, Options for Debugging Your Program
or GCC, gcc, Using GCC}. Because truncation functions can mask
are often easier and safer automatic techniques, such as fortification
(@pxref{Source Fortification}) and AddressSanitizer
(@pxref{Instrumentation Options,, Program Instrumentation Options, gcc, Using GCC}).
Because truncation functions can mask
application bugs that would otherwise be caught by the automatic
techniques, these functions should be used only when the application's
underlying logic requires truncation.