android_bionic/libc/arch-arm/bionic
Josh Gao 2303283740 Track whether a thread is currently vforked.
Our various fd debugging facilities get extremely confused by a vforked
process closing file descriptors in preparation to exec: fdsan can
abort, and fdtrack will delete backtraces for any file descriptors that
get closed. Keep track of whether we're in a vforked child in order to
be able to detect this.

Bug: http://b/153926671
Test: 32/64-bit bionic-unit-tests on blueline, x86_64 emulator
Change-Id: I8a082fd06bfdfef0e2a88dbce350b6f667f7df9f
2020-05-07 19:44:27 -07:00
..
__aeabi.c
__aeabi_read_tp.S
__bionic_clone.S
__restore.S
_exit_with_stack_teardown.S
atexit_legacy.c
atomics_arm.c
bpabi.c Implement __gnu_[u]ldivmod_helper methods in libc 2019-04-22 18:12:55 -07:00
exidx_dynamic.c
exidx_static.c Move dl_unwind_find_exidx from libdl.a to libc.a 2019-10-14 16:34:12 -07:00
kuser_helper_on.S
libcrt_compat.c Switch libm to libcrt.builtins 2019-02-22 13:33:15 -08:00
popcount_tab.c
setjmp.S
syscall.S
vfork.S Track whether a thread is currently vforked. 2020-05-07 19:44:27 -07:00