search for: tsan_report

~/workspace/LLVM/llvm/projects/compiler-rt/lib/tsan/rtl/tsan_report.cc: In function ‘const char* __tsan::ReportTypeString(__tsan::ReportType, __sanitizer::uptr)’: ~/workspace/LLVM/llvm/projects/compiler-rt/lib/tsan/rtl/tsan_report.cc:95:41: warning: ISO C++ does not allow ?: with omitted middle operand [-Wpedantic] return GetReportHeaderFromTag(tag) ?: "r...

...e parsing tools would be subtools of the asan, tsan, ubsan subtools. This would require the user to explicitly communicate the report type ahead of time. Command line invocation would look something like: ``` llvm-xsan asan parse < asan_report.txt > asan_report.json llvm-xsan tsan parse < tsan_report.txt > tsan_report.json llvm-xsan ubsan parse < ubsan_report.txt > ubsan_report.json ``` The structured data format would be JSON. The schema details still need to be worked out but the schema will need to cover every type of issue that a Sanitizer can find. ## Symbolication tool Sanitiz...

...ubsan subtools. >> This would require the user to explicitly communicate the report type >> ahead of time. Command line invocation would look something like: >> >> ``` >> llvm-xsan asan parse < asan_report.txt > asan_report.json >> llvm-xsan tsan parse < tsan_report.txt > tsan_report.json >> llvm-xsan ubsan parse < ubsan_report.txt > ubsan_report.json >> ``` >> >> The structured data format would be JSON. The schema details still >> need to be worked out but the schema will need to cover every type of >> issue that...