clayborg added a comment. The idea for the JSON file is that it must have a "name" (or maybe "plug-in"?) to identify which trace plug-in and a "trace-file" at the very least:
{ "name": "intel-pt", "trace-file": "/tmp/trace-info" } The "name" field would match the name of the trace plug-in in LLDB. For intel PT they need info about the CPU. Some intel PT libraries have a structure like: // A cpu vendor. enum pt_cpu_vendor { pcv_unknown, pcv_intel }; struct pt_cpu { enum pt_cpu_vendor vendor; uint16_t family; uint8_t model; uint8_t stepping; }; So the trace JSON file for intel-pt might look like: { "name": "intel-pt", "trace-file": "/tmp/a", "pt_cpu": { "vendor": "intel", "family": 10, "model": 2, "stepping": 1 } } Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D85705/new/ https://reviews.llvm.org/D85705 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits