summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/functionalities/command_source/TestCommandSource.py
diff options
context:
space:
mode:
authorJustin Bogner <mail@justinbogner.com>2016-02-08 22:49:40 +0000
committerJustin Bogner <mail@justinbogner.com>2016-02-08 22:49:40 +0000
commit34a34aa89ea19bcdb193cc0ab4a859c878ebb57b (patch)
tree058e2f9291c47cdbb9847e4d2409ec3bb8cd601a /lldb/packages/Python/lldbsuite/test/functionalities/command_source/TestCommandSource.py
parent55adc9ddcc5be3c009b8a9167bbf13109e2a9674 (diff)
downloadbcm5719-llvm-34a34aa89ea19bcdb193cc0ab4a859c878ebb57b.tar.gz
bcm5719-llvm-34a34aa89ea19bcdb193cc0ab4a859c878ebb57b.zip
llvm-cov: Fix reading gcov data that does not have function names
In order for recent gcov versions to read the coverage data, you have to use UseCfgChecksum=true and FunctionNamesInData=false options for coverage profiling pass. This is because gcov is expecting the function section in .gcda to be exactly 3 words in size, containing ident and two checksums. While llvm-cov is compatible with UseCfgChecksum=true, it always expects a function name in .gcda function sections (it's not compatible with FunctionNamesInData=false). Thus it's currently impossible to generate one set of coverage files that works with both gcov and llvm-cov. This change fixes the reading of coverage information to only read the function name if it's present. Patch by Arseny Kapoulkine. Thanks! llvm-svn: 260162
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/functionalities/command_source/TestCommandSource.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud