jingham added a comment. Are you planning to rewrite this the command part of this patch using the changes from https://reviews.llvm.org/D44603 once that's approved?
I like the fact that the part of this that prints exception objects gets access to them through the thread, not the frame. Even though the implementation in https://reviews.llvm.org/D44603 only knows how to get the exception object at the point of throw, at some point it would be nice to support the scenario where you stop sayin a breakpoint on a destructor that's getting run as the stack is unwound due to an exception, and we can tell you what exception is currently propagating. For that purpose, asking the thread seems right. https://reviews.llvm.org/D43886 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
