Searched refs:reentrancy (Results 1 – 16 of 16) sorted by relevance
18 static reentrancy_t reentrancy; variable62 return reentrancy != non_reentrant; in test_is_reentrant()109 malloc_printf("%s (%s): %s\n", test_name, reentrancy_t_str(reentrancy), in p_test_fini()133 reentrancy = non_reentrant; in p_test_impl()141 reentrancy = libc_reentrant; in p_test_impl()149 reentrancy = arena_new_reentrant; in p_test_impl()
66 # meaning as normal reentrancy on other platforms. See the z/OS documentation
27 competing threads; however, they are not designed to handle reentrancy
796 Real world examples of reentrancy are more likely to involve multiple
1524 #define UNLOCK_RETURN(tsdn, ret, reentrancy) \ argument1525 malloc_init_hard_cleanup(tsdn, reentrancy); \
172 functools.lru_cache() was susceptible to an obscure reentrancy bug
620 avoid possible reentrancy issues.
64 functools.lru_cache() was susceptible to an obscure reentrancy bug caused by
971 functools.lru_cache() was susceptible to an obscure reentrancy bug
330 avoid possible reentrancy issues.
693 make in certain cases to *e.g.* avoid accidental reentrancy in user code.
468 17.6.4.6 [reentrancy]
959 // avoid the risk of reentrancy leading to the callback being
148 - Add missing reentrancy support for custom extent hooks which allocate.
3448 * xmlregexp.c: fixed bug #310264, basically it's about reentrancy14028 * python/libxml.c: fixed a possible reentrancy problem19345 reentrancy problem at printing. One is left in entities.c, to
11441 and reentrancy safety