clayborg wrote: > I am not a big fan of having a specialized name `separate-debug-info` to dump > external debug info. Ideally, I would like a single/centralized command for > end users to see/check symbols/debug info status for a target including all > possible situations. > > How about we rename this as a more generic command name (like `target module > dump syminfo` or `target symbols dump`) which can be extended to include more > than dwo/N_OSO scenarios: > > * Status of dwo structures (like this) > * External dSYM files and .debuginfo files status (missing or not) > * Embedded symbol status: like symbol table only, debug info + symbol table, > debug info only + symbol table stripped. > * dwp files > > The benefit is that this provides a central command to dump all symbol file > status instead of several commands to gather info. > > I do not think the above should be included in this patch but at least the > command name opens the possibility for extension in future. > > Another option is treating `image list` to be the central command mentioned > above. And adding new options for `image list` to include dwo/N_OSO, > external/embedded symbol/debuginfo status etc... I believe most Windows > debuggers (like windbg) use this approach. > > What do you guys think?
I would rather keep this kind of thing separate as the format we want to output here. It would be find to go and modify these other commands to include exceptional issues found from the structured data and fit the data into the output structure of each of those commands if they can use it. 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
