Home
last modified time | relevance | path

Searched refs:failure (Results 1 – 8 of 8) sorted by relevance

/bionic/libc/include/bits/
Dstdatomic.h208 desired, success, failure) \ argument
210 success, failure)
212 desired, success, failure) \ argument
214 success, failure)
/bionic/docs/
Dstatus.md76 * 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
Dlibc_assembler.md137 * Verify the routine handles unaligned buffers properly. Usually, a failure
/bionic/libc/kernel/uapi/linux/
Dkfd_ioctl.h184 struct kfd_memory_exception_failure failure; member
Daudit.h333 __u32 failure; member
/bionic/libc/kernel/
DREADME.md9 declarations and constructs that usually result in compilation failure.
/bionic/libc/malloc_debug/
DREADME.md385 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/libdl/
DNOTICE162 work stoppage, computer failure or malfunction, or any and all