A program under tsan does much more than a normal one, even memory accesses are
not fully async-signal-safe. So a correct program that uses fork can hang under
tsan.
This needs to be fixed one way or another.
There are 2 competing proposals.
One is to lock all internal mutexes before fork:
http://llvm-reviews.chandlerc.com/D2470
Another is to disable memory access and sync action processing after fork in
multithreaded program (expecting it to exec soon). For single-threaded programs
we can continue to work as usual.
Original issue reported on code.google.com by dvyu...@google.com on 9 Jan 2014 at 5:05
Original issue reported on code.google.com by
dvyu...@google.com
on 9 Jan 2014 at 5:05