Open Bug 1371009 Opened 3 years ago Updated 3 years ago

Figure out why instrumenting with GCOV affects memory operations.


(Testing :: Code Coverage, enhancement)

Not set


(Not tracked)


(Reporter: sparky, Unassigned)



This bug is for determining why tests that test memory functionality or that gather performance data about the memory fail. One example of this is when we attempt to collect GCOV code coverage information from the AWSY test suite on the linux64-ccov build. In that problem, bug 1353882, there is a certain type of memory that is being searched for with the path starting as 'explicit/heap-unclassified' that is empty when it should contain some items. There is another issue with the arena allocator as well that was patched in bug 1370242 (problem wasn't solved, only prevented).
You need to log in before you can comment on or make changes to this bug.