fortify-headers/include/stdlib.h, branch 0.6 Standalone portable header-based implementation of FORTIFY_SOURCE=3 http://git.dustri.org/fortify-headers/atom?h=0.6 2015-06-03T17:55:35Z Use namespace-safe macro, param and variable names 2015-06-03T17:55:35Z Trutz Behn 2015-06-03T17:27:01Z urn:sha1:1cd5461a5375207602f2cbdfd9a50a9b751cb7c8 Add LICENSE header 2015-05-13T11:15:36Z sin 2015-05-13T11:15:36Z urn:sha1:07adb509146e4185b9b7587baad26cdfb766c67e Add fortify_fn() helper in fortify-headers.h 2015-05-13T11:05:29Z sin 2015-05-13T11:04:15Z urn:sha1:158782b3bb791eae3c97947944c7023452bfbc96 Minor style fix 2015-05-07T17:04:01Z sin 2015-05-07T17:04:01Z urn:sha1:316a48653315b4bc36d8c50b542471b18441c9d5 fix realpath when stdlib.h is included before limits.h 2015-05-07T14:02:11Z Natanael Copa 2015-05-07T12:50:03Z urn:sha1:c2bb9e106a32619726cfc5052a1509e96b90de9f 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 Trutz Behn 2015-03-14T19:06:48Z urn:sha1:22e7e51007f3a28ded43f6cb8f0ff59a7a691175 Add __artificial__ to aid in debugging 2015-03-14T09:38:22Z sin 2015-03-14T09:38:11Z urn:sha1:37eb2c9c1d71c2ff21605ecaf46cdd926244d361 Restore C++ support 2015-03-13T23:09:15Z sin 2015-03-13T23:09:15Z urn:sha1:d12254166a55d17932ea4143fbd50fb52539ff8b Rework fortify implementation to use extern inline 2015-03-13T11:00:46Z sin 2015-03-13T11:00:46Z urn:sha1:9f8c543dc81f0c4239acae6713f5414eb7dc681d Overriding functions with macros is legal in C but a lot of software is not prepared for it. Use the extern inline method to achieve the same result. Put include guards in the reserved namespace 2015-03-11T21:33:01Z Trutz Behn 2015-03-11T18:55:51Z urn:sha1:b211796d68c4a6b56f999534627791f3576b6135 fortify-headers is considered part of the implementation.