jimingham wrote: > > Yes, part of the requirement is that the output isn't printed by lldb > > itself, although the implementer is still in control with the return value. > > Okay. I was afraid of that. :) > > The code looks good, though I must admit that the functionality seems a bit.. > random. Like, you're putting lldb in a terminal, but then you don't want it > to behave like lldb in a terminal. I don't suppose there's anything you can > say about what you intend to do with it?
One use case is that a UI might want to make a nicer presentation for some class of errors - for in particular the expression syntax errors that have more rich structure - making them disclosable or whatnot. Since those can be huge - particularly compile errors from expressions - you really don't want to duplicate the printing in that case. https://github.com/llvm/llvm-project/pull/125006 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
