clayborg wrote: > (aside: isn't the SBAPI meant to be the thing to use if you want to script > stuff, rather than having formatted output/scraping that? - but sounds like > the output has converged on a table rather than JSON anyway? So maybe a moot > point)
The reason we use StructuredData internally are for a few reasons: - we could return this through an API if desired - we want to include this data in the "statistics dump" - it stops us from having to add two new APIs to SymbolFile, one that dumps stuff to text, and one that creates structured data > Re: errors, OSO (what does that stand for anyway) - yeah, maybe separate > tables for different data? (one table for OSO, one for DWO, one for errors? > (or two for errors, one for OSO errors and one for DWO errors?)) The structured data to text in the command uses different tables now. https://github.com/llvm/llvm-project/pull/66035 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
