<?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 usage-lldb-loggings</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>e97b991e - [lldb] Remove LLDB session dir and just store test traces in the respective test build directory</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/examples/test/usage-lldb-loggings#e97b991e</link>
        <description>[lldb] Remove LLDB session dir and just store test traces in the respective test build directoryTest runs log some of their output to files inside the LLDB session dir. Thissession dir is shared between all tests, so all the tests have to make sure theychoose a unique file name inside that directory. We currently choose by default`&lt;test-class-name&gt;-&lt;test-method-name&gt;` as the log file name. However, that meansthat if not every test class in the test suite has a unique class name, then weend up with a race condition as two tests will try to write to the same logfile.I already tried in D83767 changing the format to use the test file basenameinstead (which we already require to be unique for some other functionality),but it seems the code for getting the basename didn&apos;t work on Windows.This patch instead just changes that dotest stores the log files in the builddirectory for the current test. We know that directory is unique for this test,so no need to generate some unique file name now. Also removes all theenvironment vars and parameters related to the now unused session dir.The new log paths now look like this for a failure in &apos;TestCppOperators`:```./lldb-test-build.noindex/lang/cpp/operators/TestCppOperators.test_dwarf/Failure.log./lldb-test-build.noindex/lang/cpp/operators/TestCppOperators.test_dsym/Failure.log./lldb-test-build.noindex/lang/cpp/operators/TestCppOperators.test_gmodules/Failure.log```Reviewed By: labathDifferential Revision: https://reviews.llvm.org/D92498

            List of files:
            /llvm-project-15.0.7/lldb/examples/test/usage-lldb-loggings</description>
        <pubDate>Fri, 04 Dec 2020 10:42:36 +0000</pubDate>
        <dc:creator>Raphael Isemann &lt;teemperor@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>d79f06cf - Modified .lldb-loggings now to direct the lldb log files to the same session directory which also houses the test logs.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/examples/test/usage-lldb-loggings#d79f06cf</link>
        <description>Modified .lldb-loggings now to direct the lldb log files to the same session directory which also houses the test logs.llvm-svn: 162387

            List of files:
            /llvm-project-15.0.7/lldb/examples/test/usage-lldb-loggings</description>
        <pubDate>Wed, 22 Aug 2012 20:25:33 +0000</pubDate>
        <dc:creator>Johnny Chen &lt;johnny.chen@apple.com&gt;</dc:creator>
    </item>
<item>
        <title>c50ce977 - Demonstrate how to use the config file and the pre-flight functionality to route the lldb gdb-remote log messages</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/examples/test/usage-lldb-loggings#c50ce977</link>
        <description>Demonstrate how to use the config file and the pre-flight functionality to route the lldb gdb-remote log messagesinto individually named log destinations.  In the simple usage-lldb-loggings example, we ran two cases which resultedin two lldb_log files.llvm-svn: 162378

            List of files:
            /llvm-project-15.0.7/lldb/examples/test/usage-lldb-loggings</description>
        <pubDate>Wed, 22 Aug 2012 18:48:13 +0000</pubDate>
        <dc:creator>Johnny Chen &lt;johnny.chen@apple.com&gt;</dc:creator>
    </item>
</channel>
</rss>
