https://github.com/labath commented:

I think this is one of those tests that should really be an API test. As far as 
I can tell, there's nothing darwin-specific about this bug -- except for the 
fact that building shared libraries in a cross-platform manner is hard. But the 
API tests have wrappers that let us do that, and they even support windows. (I 
had a feeling our docs already stated that shared libraries is a reason to make 
something an API test, but I can't find that now.)

I understand the desire to not skip a test (and that making it an API test will 
make that even harder, as a crash will bring down the entire test), but I'm not 
sure if that's so useful as to override this. I also think that making a test 
which checks that something fails in a particular way can be fragile (as a 
random refactor could make it fail in a different way).

That said, thank you for reducing this. Having this around somewhere will be 
very useful for fixing this (eventually). From the looks of things, it may be 
possible to get rid of the dlopen/dlsym thing as well (replace it with hard 
shared library dependencies) -- it seems the important part is that the two 
modules have different definitions of one type, and the way that the shared 
library is loaded is beside the point.

https://github.com/llvm/llvm-project/pull/112566
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to