labath wrote: > I'm trying to figure out how to get that linked only when tests are running > and not to the LLDB binary all the time.
I don't think you can do that without building another lldb binary. We actually have something like that in the form of the [lldb-test binary](https://github.com/llvm/llvm-project/tree/main/lldb/tools/lldb-test). It's not an actual lldb, but it links all of the same components, and it shouldn't be a big problem to add a new component that's only used in lldb-test. I think it would be reasonable to add a new lldb-test sub-command which is designed to be used for testing the telemetry backend. However, it's use tends to be somewhat cumbersome because you have to write some code do something, and then also drive that code from the command line. I would recommend trying to test as much as possible via the unit tests (which are basically can do anything that lldb-test can, but you don't have to drive them from the command line), and use only when you really need an end-to-end experience. https://github.com/llvm/llvm-project/pull/127696 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
