http://llvm.org/bugs/show_bug.cgi?id=20986
Bug ID: 20986
Summary: gcda (gcov data) writer is not multi-process-safe,
impacting coverage analysis and profiling of programs
that fork()
Product: compiler-rt
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: compiler-rt
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Classification: Unclassified
llvm/projects/compiler-rt/lib/profile/GCDAProfiling.c says:
|* TODO: gcov is multi-process safe by having each exit open the existing file
|* and append to it. We'd like to achieve that and be thread-safe too.
(http://llvm.org/viewvc/llvm-project/compiler-rt/trunk/lib/profile/GCDAProfiling.c?revision=215933&view=markup#l18)
I believe that this is causing a problem for test coverage analysis when the
test framework implements death tests in the way that gtest (googletest) does,
either as fork()-based or fork()-exec()-based. These are described as “fast”
and “threadsafe” respectively in
https://code.google.com/p/googletest/wiki/AdvancedGuide#How_It_Works.
Regardless, I didn’t find a bug tracking this TODO, and it seems like there
should probably be one.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
LLVMbugs mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
