| 532d6f09b1e7bfe995c1dba6594d1fc2c1ea77cf |
|
02-May-2013 |
Nick Kralevich <nnk@google.com> |
Use __predict_false on some fortify methods.
Give the compiler some hints that these error conditions
are unlikely to occur in practice.
Change-Id: Ifaf7322a12120ef663c8315c1a18c2dcbe4bda23
|
| 8f2a5a0b40fc82126c691d5c30131d908772aab7 |
|
15-Mar-2013 |
Elliott Hughes <enh@google.com> |
Clean up internal libc logging.
We only need one logging API, and I prefer the one that does no
allocation and is thus safe to use in any context.
Also use O_CLOEXEC when opening the /dev/log files.
Move everything logging-related into one header file.
Change-Id: Ic1e3ea8e9b910dc29df351bff6c0aa4db26fbb58
|
| 326ea5413d18ea019cd1bda415ce428f7bdcafd2 |
|
04-Dec-2012 |
Nick Kralevich <nnk@google.com> |
clean up FORTIFY_SOURCE handling.
Avoid duplicating huge chunks of code.
Change-Id: Id6145cdfce781c5ffba2abaaa79681d25a7ab28f
|
| 4035b7a32155eac46f3f3782774deb5967ea2b54 |
|
23-Oct-2012 |
Elliott Hughes <enh@google.com> |
Move the FORTIFY_SOURCE helpers over to .cpp.
Change-Id: Ib5067d51b983cac7760c975becce7fe2408ead04
|