beanz accepted this revision.
beanz added a comment.

One small comment below. In general I agree with the thoughts here, and I think 
that this is a huge step forward for testing the debug server components.

I also agree with Zachary in principal that it would be nice to come up with 
lit-based test harnesses for more parts of LLDB, although I'm skeptical about 
whether or not that is actually the best way to test the debug server pieces. 
Either way, this is a huge step forward from what we have today, so we should 
go with it.



================
Comment at: unittests/tools/CMakeLists.txt:1
+if(UNIX AND NOT APPLE)
+  add_subdirectory(lldb-server)
----------------
labath wrote:
> This is not what I meant. The only targets (at least until we have 
> debugserver support) that can realistically pass these tests are linux, 
> android, and netbsd. The other targets (right now, I guess that would mean 
> freebsd) don't even pretend to support debugging via lldb-server, so we 
> should not fail their build because of that. Check for usages of 
> CMAKE_SYSTEM_NAME to see how to discriminate those.
Darwin pretends to support lldb-server in several places, it would be nice to 
be able to run these tests on Darwin if they work. One of my big goals for the 
future of testing on LLDB is to get to the point where the only differences in 
test coverage when running tests on different hosts is truly platform-specific 
code. Today we are nowhere near that.

Also, as Pavel pointed out in email, the lldb-server tests are also run against 
debugserver, so we need to make sure that still works too.


https://reviews.llvm.org/D32930



_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to