<?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 macho-invalid-loadfvmlib-obsolete</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>bc5c29a6 - Another additional error check for invalid Mach-O files for the</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/Object/Inputs/macho-invalid-loadfvmlib-obsolete#bc5c29a6</link>
        <description>Another additional error check for invalid Mach-O files for theobsolete load commands.Again the philosophy of the error checking in libObject forMach-O files, the idea behind the checking is that we neverwill return a Mach-O file out of libObject that contains unknownthings the library code can&#8217;t operate on.  So known obsoleteload commands will cause a hard error.Also to make things clear I have added comments to thevalues and structures in Support/Mach-O.h andSupport/MachO.def as to what is obsolete.As noted in a TODO in the code, there may need to be anon-default mode to allow some unknown values for wellstructured Mach-O files with things like unknown loadload commands.  So things like using an old lldb on a newerMach-O file could still provide some limited functionality.llvm-svn: 285342

            List of files:
            /llvm-project-15.0.7/llvm/test/Object/Inputs/macho-invalid-loadfvmlib-obsolete</description>
        <pubDate>Thu, 27 Oct 2016 20:59:10 +0000</pubDate>
        <dc:creator>Kevin Enderby &lt;enderby@apple.com&gt;</dc:creator>
    </item>
</channel>
</rss>
