Michael137 wrote: > Maybe, but I don't expect the test to be pretty. What I (sometimes) do in > these cases is to make the test bidirectional, i.e., have two compile unit > where each one has a definition for a type declared/used in the other one. > This way, you're guaranteed to hit the error code path regardless of the > order of the two units. This is easier to do if you don't actually need to > run the binary (which you probably don't need to do here).
Great idea, let me try this out https://github.com/llvm/llvm-project/pull/120569 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
