<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in module.modulemap</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>d48ef7ca - [lldb] Print full Clang diagnostics when the ClangModulesDeclVendor fails to compile a module</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/lang/objc/modules-compile-error/module.modulemap#d48ef7ca</link>
        <description>[lldb] Print full Clang diagnostics when the ClangModulesDeclVendor fails to compile a moduleSummary:When the ClangModulesDeclVendor currently fails it just prints very basic and often incomplete diagnostics without any source locations:```(lldb) p @import Foundationerror: while importing modules:&apos;foo/bar.h&apos; file not foundcould not build module &apos;Darwin&apos;[...]```or even just```(lldb) p @import Foundationerror: while importing modules:could not build module &apos;Darwin&apos;[...]```These diagnostics help neither the user nor us with figuring out what is the reason for the failure.This patch wires up a full TextDiagnosticPrinter in the ClangModulesDeclVendor and makessure we always return the error stream to the user when we fail to compile our modules.Fixes rdar://63216849Reviewers: aprantl, jdoerfertReviewed By: aprantlSubscribers: JDevlieghereDifferential Revision: https://reviews.llvm.org/D79947

            List of files:
            /llvm-project-15.0.7/lldb/test/API/lang/objc/modules-compile-error/module.modulemap</description>
        <pubDate>Fri, 15 May 2020 07:29:38 +0000</pubDate>
        <dc:creator>Raphael Isemann &lt;teemperor@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
