[llvm-dev] Status of debuginfo-tests

[David Blaikie via llvm-dev]

It's used, but not a huge repository of things, as you can see. I think
I've run it once or twice, but a long time ago. It was introduced for/by
Apple/LLDB stuff, so it's not something I've paid much attention to.

It's probably not suitable as part of llvm tests directly. Those tests are
designed to be shorter/narrower/more focussed than full integration tests
(we don't execute any compiled programs under test there, for example).

Porting to lit seems probably fine/good.

On Thu, Sep 7, 2017 at 11:23 AM Zachary Turner <zturner at google.com> wrote:

> What is the status of debuginfo-tests?  Is it actively supported?  How do
> you run it?  It doesn't appear to be based on lit, any particular reason?
> Why is it its own repo instead of being part of llvm repo?
>
> I'd like improve this to support CodeView and PDB, such that it would only
> run on Windows and only if a suitable debugger was found (probably
> WinDbg).  WinDbg supports a JavaScript-based scripting model, similar to
> how LLDB supports a Python based model, so my thoughts were to have a
> lit-based runner that scans for .js files that contain a test script
> alongside some source, then build the program, run it in WinDbg with some
> script that does various things, and exits the debugger, moving on to the
> next test.
>
> Anything I should be aware of / careful of when messing around in here?
> And any reason it can't be moved to llvm/tests and ported to lit?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170907/e5d0835a/attachment.html>