oontvoo wrote:
> This is why I suggested way back to focus on SetExecutableModule, as that is > (one) place where all of these paths converge, and it covers the most > expensive part of the operation. I don't think it's the only way to capture > all this information, but I still think it's _a_ way to do it. However, it's > definitely not the same as "loading/creating a target". Thanks for the example! THat makes a lot more sense now. I've updated the patch to : - Use separate entries for describing the Main-executable and for the process-exit - Rename the struct as suggested About the `exec*()` use case, would be nice to be able to have *something* to uniquely identify each image ... but i'm not sure what it is ... for now they would just have to be duplicate entries (same module id) https://github.com/llvm/llvm-project/pull/127834 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
