On Sat, May 17, 2014 at 11:12 AM, 'Alexander Potapenko' via address-sanitizer <[email protected]> wrote: > We don't have any such tools yet, but you can hack something on top of one > of the existing source highlighting scripts for gcov (which I'm not familiar > to, unfortunately) > > On May 17, 2014 12:03 AM, "Hajime Morrita" <[email protected]> wrote: >> >> Hi, >> >> I just noticed that ASAN go code coverage support [1]. This is great! And >> I'm wondering how I can generate highlighted source code from this data, to >> indicate covered/uncovered code paths. That data would be pretty useful to >> improve code coverage of automated tests. >> >> The generated output from sancov.py and llvm-symbolizer contains only the >> line number of the basic block beginning, but it does not contain one of the >> ending of the basic block. I'd like to know how to figure out the line >> numbers of the bb ends,
I don't think this is currently possible. The (experimental!) asan-coverage dumps PCs on disk and then llvm-symbolizer translates PCs to the line numbers -- but not to the line ranges. --kcc >> so that I can highlight the code of each bb >> begin/end pair. >> >> Any advice would be appreciated. -- You received this message because you are subscribed to the Google Groups "address-sanitizer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
