On Sun, Apr 30, 2017 at 7:23 PM, Martin Sebor wrote:
> The warning is triggered by the fscanf function being decorated
> with attribute warn_unused_result in the header. The
> header is part of libc, not GCC, so the appropriate place to
> raise a concern with it would on the libc mailing list (s
On 04/29/2017 11:50 AM, Sebastian Noack wrote:
Hi everybody,
If you use -D_FORTIFY_SOURCE=2 (or 1), some additionally checks, both,
at compile- and run-time, supposed to catch buffer overflows, are
performed. Debian (and some other distributions) use this option by
default, when packaging softwa
Hi everybody,
If you use -D_FORTIFY_SOURCE=2 (or 1), some additionally checks, both,
at compile- and run-time, supposed to catch buffer overflows, are
performed. Debian (and some other distributions) use this option by
default, when packaging software. And since I generally build my code
with -Wer
