jimingham wrote: There are other ways you could extend this that would be very fun. For instance, we could make any command that conses up its result just by calling the ValueObjectPrinter on some ValueObject to also stuff that ValueObject to the command return. Then we could add SBCommandResultObject::GetReturnValueObject to return that ValueObject. Then the callback could check whether there was a ValueObject in the command result, and if there is it would suppress that textual output and render the ValueObject as a live object in the result slot in the command output it is building up.
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
