jingham added a comment. As Greg said, iOS (and macOS as well, though less directly) have the notion of bundleID. At present, lldb doesn't directly use/figure out the bundle ID, though it could either from the binary itself or from debugserver, which does have to know that. As far as I know we always also have the path, the bundle ID is inferred from the App package the binary path points to. So that complication should not be present on iOS.
Anyway, I don't see any problem with fetching and displaying the bundleID. I don't think it would be good to make it hard to see the actual path (if you have it) as well as the bundle ID. If you are working on system components, you want to know that you are running some hand-built copy of a binary and not the pre-installed one. So we want to make it easy to see "which thing with this bundleID am I actually running". Other than that this seems fine to me. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D68968/new/ https://reviews.llvm.org/D68968 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
