2303283740
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 |
||
|---|---|---|
| .. | ||
| __bionic_clone.S | ||
| __set_tls.c | ||
| _exit_with_stack_teardown.S | ||
| setjmp.S | ||
| syscall.S | ||
| vfork.S | ||