[Lldb-commits] [PATCH] Add SBArgs to the public interface

Zachary Turner zturner at google.com
Wed Mar 11 17:41:07 PDT 2015

I will work on making this happen on the CMake side, so it should work for
all platforms that build with CMake.  I will need some help getting this
tied into the Xcode build, but we can revisit that after it's done on the
CMake side.

On Wed, Mar 11, 2015 at 3:58 PM Greg Clayton <clayborg at gmail.com> wrote:

> gtest would be my vote. There are bound to be things we need to test that
> aren't in the API and this is a good way to do this.
> The other thing I can think if is if, for debug builds only, we add a
> static function that is available in the public API that we can call from
> our test suite. Then we have a python based test that just does something
> like:
> static void SBDebugger::RunUnitTests();
> #endif
> The in python:
> debugger.UnitTest()
> This runs all built in unit test. These tests might need a output format
> that can be parsed in case any built in unit test fail. Then all classes
> that want to run unit tests can register a <classname::UnitTest() static
> function that can be run.
> http://reviews.llvm.org/D8265
>   http://reviews.llvm.org/settings/panel/emailpreferences/
> _______________________________________________
> lldb-commits mailing list
> lldb-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20150312/9bdd052e/attachment.html>

More information about the lldb-commits mailing list