tberghammer added a comment. I think to get a very good coverage for the basic functionalities we need some sort of stress testing or fuzzing infrastructure because the most issues I hit come from compilers generating something a bit different then we are expecting. For stack unwinding I added a stress test (TestStandardUnwind.py, working on arm and aarch64) what catches a lot of bugs but running it takes so long that it can't be added to the everyday test suit. Should we try to design a fuzz testing infrastructure what runs on a build bot so we don't have to depend on the fuzz testing behavior of the normal test suit?
http://reviews.llvm.org/D16334 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
