Searched refs:failure (Results 1 – 10 of 10) sorted by relevance
| /bionic/libc/include/bits/ |
| D | stdatomic.h | 208 desired, success, failure) \ argument
210 success, failure)
212 desired, success, failure) \ argument
214 success, failure)
|
| /bionic/docs/ |
| D | status.md | 76 * Using `%n` with the printf family is now reported as a FORTIFY failure.
107 runtime and reported as a FORTIFY failure.
109 reported as a FORTIFY failure.
136 reported as a FORTIFY failure. Most commonly this is a result of confusing
|
| D | libc_assembler.md | 137 * Verify the routine handles unaligned buffers properly. Usually, a failure
|
| D | NOTICE | 162 work stoppage, computer failure or malfunction, or any and all
|
| /bionic/libc/kernel/uapi/linux/ |
| D | audit.h | 335 __u32 failure; member
|
| D | kfd_ioctl.h | 184 struct kfd_memory_exception_failure failure; member
|
| /bionic/libc/kernel/ |
| D | README.md | 9 declarations and constructs that usually result in compilation failure.
|
| /bionic/libc/malloc_debug/ |
| D | README.md | 385 04-15 12:00:31.305 7412 7412 E malloc_debug: Backtrace at time of failure:
430 04-15 12:00:31.305 7412 7412 E malloc_debug: Backtrace at time of failure:
449 04-15 12:00:31.305 7412 7412 E malloc_debug: Backtrace at time of failure:
|
| /bionic/apex/ |
| D | NOTICE | 162 work stoppage, computer failure or malfunction, or any and all
|
| /bionic/build/ |
| D | NOTICE | 162 work stoppage, computer failure or malfunction, or any and all
|