[llvm-dev] [cfe-dev] RFC: CodeView debug info emission in Clang/LLVM

[Zachary Turner via llvm-dev]

On Tue, Nov 3, 2015 at 4:25 PM Dave Bartolomeo <
Dave.Bartolomeo at microsoft.com> wrote:

> The LLVMCodeView library is definitely independent of the rest of the
> design questions.
>
>
>
> As far as testing goes, what would be the conventional LLVM way of testing
> a library for file format manipulation? A test tool that converts some
> simple text form into a .obj containing CodeView sections, and comparing
> with a baseline .obj? Or would the test convert back from the .obj to some
> kind of text as well, and compare to a text baseline? Is there some other
> LLVM component that has similar testing requirements that I can use as an
> example for how to test LLVMCodeView? Note that I’d be adding a
> CodeView->text dump tool anyway, since that will be pretty much essential
> for anyone working with CodeView.
>
>
>
> -Dave
>
David Majnemer and David Blaikie (this is seriously like the attack of the
Daves) probably have some thoughts, but currently there is code in
llvm-readobj.exe to parse certain types of codeview from object files
(mostly line table information).

So one idea is to generate some object files that have CV records you know
about up front, then pass the output of llvm-readobj (which would need to
be updated to use LLVMCodeView instead of hand-rolled parsing) to FileCheck
and verify that it matches some pattern.

Maybe the Daves have some other ideas as well.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20151104/341580d5/attachment.html>