[Lldb-commits] [lldb] [lldb] Support CommandInterpreter print callbacks (PR #125006)

[via lldb-commits]

jimingham wrote:

Man there's a lot of boiler plate in hooking up to SWIG...  But this all looks right to me.  

I wondered whether the callback would benefit from knowing whether the result had been dumped immediately or not, but I can't think of a good reason for that.

If this result printing callback was also passed the command string (which it has from just above where the callback is called) then this would also be an easy way to do logging of command execution.  That's not needed for your current purpose, but would add another strong motivation for this change...

https://github.com/llvm/llvm-project/pull/125006