jimingham wrote: N_SO is the stab moniker for a source file, and N_OSO is the object file associated with that source file (N_SO was in Sun's implementation, we made up N_OSO). Most nm''s leave off the N_ when they print stabs, so then this became just OSO...
We don't do DWO on Darwin, and nobody but Darwin does OSO's, so for now I don't think you need to worry about mixing of the entities in these reports. Jim > On Sep 20, 2023, at 3:10 PM, David Blaikie ***@***.***> 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) > > 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?)) > > — > Reply to this email directly, view it on GitHub > <https://github.com/llvm/llvm-project/pull/66035#issuecomment-1728492544>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/ADUPVW7ZIZJ2T6I6RHFFENLX3NSWVANCNFSM6AAAAAA4UCOLGY>. > You are receiving this because you were mentioned. > 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
