fortify-headers/include/stdlib.h, branch 0.8

Only include limits.h when actually used

2016-07-14T15:09:13Z

The __extension__ seems to trigger a bug in gcc when there are no identifier specified afterwards. Testcase: echo "#include " > try.c && cc -O0 -c try.c try.c:2:0: error: expected identifier or '(' at end of input With -O2 it does not happen. We work around this by only pulling in limits.h when we actually need the PATH_MAX. Signed-off-by: Natanael Copa

Only crash on overflow for realpath()

2015-07-16T10:45:19Z

Add extension mark to include_next to silence -pedantic

2015-06-25T09:18:26Z

Signed-off-by: Steven Barth

Use namespace-safe macro, param and variable names

2015-06-03T17:55:35Z

Add LICENSE header

2015-05-13T11:15:36Z

Add fortify_fn() helper in fortify-headers.h

2015-05-13T11:05:29Z

Minor style fix

2015-05-07T17:04:01Z

fix realpath when stdlib.h is included before limits.h

2015-05-07T14:02:11Z

If program includes stdlib.h before limits.h without _XOPEN_SOURCE, _GNU_SOURCE or _BSD_SOURCE explicitly set, then will it always trigger the trap with musl libc. This is becase stdlib.h will pull in features.h which will set _GNU_SOURCE. This means that the fortify stdlib.h will not include limits.h but it will still trigger the fortified realpath(), but without PATH_MAX set. We fix this by including system stdlib.h before testing if limits.h should be included. Since PATH_MAX is known at compile time we can also error at compile time, instead of compiling a broken realpath().

Use typeof to in part avoid replicating function types

2015-03-14T20:37:27Z

Add artificial to aid in debugging

2015-03-14T09:38:22Z