Author: dim
Date: Mon Dec 18 11:46:56 2017
New Revision: 321016
URL: http://llvm.org/viewvc/llvm-project?rev=321016&view=rev
Log:
Fix more inconsistent line endings. NFC.
Modified:
lldb/trunk/www/build.html
lldb/trunk/www/test.html
Modified: lldb/trunk/www/build.html
URL:
http://llvm.org/viewvc/llvm-project/lldb/trunk/www/build.html?rev=321016&r1=321015&r2=321016&view=diff
==============================================================================
--- lldb/trunk/www/build.html (original)
+++ lldb/trunk/www/build.html Mon Dec 18 11:46:56 2017
@@ -123,20 +123,20 @@
</li>
</ul>
Sample command line:<br/>
- <code>cmake -G Ninja -DLLDB_TEST_DEBUG_TEST_CRASHES=1
-DPYTHON_HOME=C:\Python35
-DLLDB_TEST_COMPILER=d:\src\llvmbuild\ninja_release\bin\clang.exe
..\..\llvm</code>
- <h2>Working with both Ninja and MSVC</h2>
- <p>
- Compiling with <code>ninja</code> is both faster and simpler
than compiling with MSVC, but chances are you still want
- to debug LLDB with MSVC (at least until we can debug LLDB on
Windows with LLDB!). One solution to this is to run
- <code>cmake</code> twice and generate the output into two
different folders. One for compiling (the <code>ninja</code>
- folder), and one for editing / browsing / debugging (the MSVC
folder).
- </p>
- <p>
- To do this, simply run <code>`cmake -G Ninja
<arguments>`</code> from one folder, and
- <code>`cmake -G "Visual Studio 14 2015"
<arguments>`</code> in another folder. Then you can open the .sln file
- in Visual Studio, set <code>lldb</code> as the startup project,
and use F5 to run it. You need only edit the project
- settings to set the executable and the working directory to
point to binaries inside of the <code>ninja</code> tree.
- </p>
+ <code>cmake -G Ninja -DLLDB_TEST_DEBUG_TEST_CRASHES=1
-DPYTHON_HOME=C:\Python35
-DLLDB_TEST_COMPILER=d:\src\llvmbuild\ninja_release\bin\clang.exe
..\..\llvm</code>
+ <h2>Working with both Ninja and MSVC</h2>
+ <p>
+ Compiling with <code>ninja</code> is both faster and simpler
than compiling with MSVC, but chances are you still want
+ to debug LLDB with MSVC (at least until we can debug LLDB on
Windows with LLDB!). One solution to this is to run
+ <code>cmake</code> twice and generate the output into two
different folders. One for compiling (the <code>ninja</code>
+ folder), and one for editing / browsing / debugging (the MSVC
folder).
+ </p>
+ <p>
+ To do this, simply run <code>`cmake -G Ninja
<arguments>`</code> from one folder, and
+ <code>`cmake -G "Visual Studio 14 2015"
<arguments>`</code> in another folder. Then you can open the .sln file
+ in Visual Studio, set <code>lldb</code> as the startup project,
and use F5 to run it. You need only edit the project
+ settings to set the executable and the working directory to
point to binaries inside of the <code>ninja</code> tree.
+ </p>
</div>
</div>
<div class="post" id="BuildingLldbOnMacOSX">
Modified: lldb/trunk/www/test.html
URL:
http://llvm.org/viewvc/llvm-project/lldb/trunk/www/test.html?rev=321016&r1=321015&r2=321016&view=diff
==============================================================================
--- lldb/trunk/www/test.html (original)
+++ lldb/trunk/www/test.html Mon Dec 18 11:46:56 2017
@@ -27,13 +27,13 @@
both the LLDB command line interface and the scripting API.
</p>
</div>
- <h1 class="postheader">Running tests</h1>
+ <h1 class="postheader">Running tests</h1>
<div class="postcontent">
<h2>Running the full test suite</h2>
<p>
- <strong>Windows Note</strong>: In the examples that follow, any
invocations of <code>python</code>
- should be replaced with <code>python_d</code>, the debug
interpreter, when running the test
- suite against a debug version of LLDB.
+ <strong>Windows Note</strong>: In the examples that follow, any
invocations of <code>python</code>
+ should be replaced with <code>python_d</code>, the debug
interpreter, when running the test
+ suite against a debug version of LLDB.
</p>
<p>
The easiest way to run the LLDB test suite is to use the
<tt>check-lldb</tt> build
@@ -134,93 +134,93 @@
<h1 class="postheader">Debugging test failures</h1>
<div class="postcontent">
<h2>Non-Windows platforms</h2>
- <p>
- On non-Windows platforms, you can use the <code>-d</code> option
to <code>dotest.py</code> which will cause the script to wait
+ <p>
+ On non-Windows platforms, you can use the <code>-d</code> option
to <code>dotest.py</code> which will cause the script to wait
for a while until a debugger is attached.
</p>
- <h2>Windows</h2>
+ <h2>Windows</h2>
<p>
- On Windows, it is strongly recommended to use <a
href="https://github.com/Microsoft/PTVS/releases";>Python Tools for Visual
Studio</a>
- for debugging test failures. It can seamlessly step between
native and managed code, which is very helpful when you need to step
- through the test itself, and then into the LLDB code that backs
the operations the test is performing. A quick guide to getting
- started with PTVS is as follows:
- <ul>
- <li>Install PTVS</li>
- <li>
- Create a Visual Studio Project for the Python code.
- <ul>
- <li>Go to File -> New -> Project -> Python -> From
Existing Python Code.</li>
- <li>Choose <code>llvm/tools/lldb</code> as the directory
containing the Python code.</li>
- <li>
- When asked where to save the <code>.pyproj</code> file,
choose the folder <code>llvm/tools/lldb/pyproj</code>.
- This is a special folder that is ignored by the
<code>.gitignore</code> file, since it is not checked in.
- </li>
- </ul>
- </li>
- <li>Set <code>test/dotest.py</code> as the startup file</li>
- <li>
- Make sure there is a Python Environment installed for your
distribution. For example, if you installed Python to
- <code>C:\Python35</code>, PTVS needs to know that this is
the interpreter you want to use for running the test suite.
- <ul>
- <li>Go to Tools -> Options -> Python Tools -> Environment
Options</li>
- <li>Click Add Environment, and enter <code>Python 3.5
Debug</code> for the name. Fill out the values correctly.</li>
- </ul>
- </li>
- <li>
- Configure the project to use this debug interpreter.
- <ul>
- <li>Right click the Project node in Solution Explorer</li>
- <li>In the <code>General</code> tab, Make sure
<code>Python 3.5 Debug</code> is the selected Interpreter.</li>
- <li>In <code>Debug/Search Paths</code>, enter the path to
your <code>ninja/lib/site-packages</code> directory.</li>
- <li>
- In <code>Debug/Environment Variables</code>, enter<br/>
- <code>VCINSTALLDIR=C:\Program Files (x86)\Microsoft
Visual Studio 14.0\VC\</code>
- </li>
- <li>
- If you want to enabled mixed mode debugging, check
<code>Enable native code debugging</code> (this slows down debugging,
- so enable it only on an as-needed basis.)
- </li>
- </ul>
- </li>
- <li>
- Set the command line for the test suite to run.
- <ul>
- <li>Right click the project in solution explorer and
choose the <code>Debug</code> tab.</li>
- <li>Enter the arguments to <code>dotest.py</code>. Note
you must add <code>--no-multiprocess</code></li>
- <li>
- Example command options:
- <code>
- <br/># quiet mode
- <br/>-q
- <br />--arch=i686
- <br /># Path to debug lldb.exe
- <br />--executable D:/src/llvmbuild/ninja/bin/lldb.exe
- <br /># Directory to store log files
- <br />-s D:/src/llvmbuild/ninja/lldb-test-traces
- <br />-u CXXFLAGS -u CFLAGS
- <br /># If a test crashes, show JIT debugging dialog.
- <br />--enable-crash-dialog
- <br /># Path to release clang.exe
- <br />-C d:\src\llvmbuild\ninja_release\bin\clang.exe
- <br /># Path to the particular test you want to debug.
- <br />-p TestPaths.py
- <br /># Root of test tree
- <br
/>D:\src\llvm\tools\lldb\packages\Python\lldbsuite\test
- <br /># Required in order to be able to debug the test.
- <br />--no-multiprocess
- </code>
- </li>
- <li>
- As copy-pastable command line:<br/>
- <code>
- -q --arch=i686 --executable
D:/src/llvmbuild/ninja/bin/lldb.exe -s D:/src/llvmbuild/ninja/lldb-test-traces
- -u CXXFLAGS -u CFLAGS --enable-crash-dialog -C
d:\src\llvmbuild\ninja_release\bin\clang.exe
- -p TestPaths.py
D:\src\llvm\tools\lldb\packages\Python\lldbsuite\test --no-multiprocess
- </code>
- </li>
- </ul>
- </li>
- </ul>
+ On Windows, it is strongly recommended to use <a
href="https://github.com/Microsoft/PTVS/releases";>Python Tools for Visual
Studio</a>
+ for debugging test failures. It can seamlessly step between
native and managed code, which is very helpful when you need to step
+ through the test itself, and then into the LLDB code that backs
the operations the test is performing. A quick guide to getting
+ started with PTVS is as follows:
+ <ul>
+ <li>Install PTVS</li>
+ <li>
+ Create a Visual Studio Project for the Python code.
+ <ul>
+ <li>Go to File -> New -> Project -> Python -> From
Existing Python Code.</li>
+ <li>Choose <code>llvm/tools/lldb</code> as the directory
containing the Python code.</li>
+ <li>
+ When asked where to save the <code>.pyproj</code> file,
choose the folder <code>llvm/tools/lldb/pyproj</code>.
+ This is a special folder that is ignored by the
<code>.gitignore</code> file, since it is not checked in.
+ </li>
+ </ul>
+ </li>
+ <li>Set <code>test/dotest.py</code> as the startup file</li>
+ <li>
+ Make sure there is a Python Environment installed for your
distribution. For example, if you installed Python to
+ <code>C:\Python35</code>, PTVS needs to know that this is
the interpreter you want to use for running the test suite.
+ <ul>
+ <li>Go to Tools -> Options -> Python Tools -> Environment
Options</li>
+ <li>Click Add Environment, and enter <code>Python 3.5
Debug</code> for the name. Fill out the values correctly.</li>
+ </ul>
+ </li>
+ <li>
+ Configure the project to use this debug interpreter.
+ <ul>
+ <li>Right click the Project node in Solution Explorer</li>
+ <li>In the <code>General</code> tab, Make sure
<code>Python 3.5 Debug</code> is the selected Interpreter.</li>
+ <li>In <code>Debug/Search Paths</code>, enter the path to
your <code>ninja/lib/site-packages</code> directory.</li>
+ <li>
+ In <code>Debug/Environment Variables</code>, enter<br/>
+ <code>VCINSTALLDIR=C:\Program Files (x86)\Microsoft
Visual Studio 14.0\VC\</code>
+ </li>
+ <li>
+ If you want to enabled mixed mode debugging, check
<code>Enable native code debugging</code> (this slows down debugging,
+ so enable it only on an as-needed basis.)
+ </li>
+ </ul>
+ </li>
+ <li>
+ Set the command line for the test suite to run.
+ <ul>
+ <li>Right click the project in solution explorer and
choose the <code>Debug</code> tab.</li>
+ <li>Enter the arguments to <code>dotest.py</code>. Note
you must add <code>--no-multiprocess</code></li>
+ <li>
+ Example command options:
+ <code>
+ <br/># quiet mode
+ <br/>-q
+ <br />--arch=i686
+ <br /># Path to debug lldb.exe
+ <br />--executable D:/src/llvmbuild/ninja/bin/lldb.exe
+ <br /># Directory to store log files
+ <br />-s D:/src/llvmbuild/ninja/lldb-test-traces
+ <br />-u CXXFLAGS -u CFLAGS
+ <br /># If a test crashes, show JIT debugging dialog.
+ <br />--enable-crash-dialog
+ <br /># Path to release clang.exe
+ <br />-C d:\src\llvmbuild\ninja_release\bin\clang.exe
+ <br /># Path to the particular test you want to debug.
+ <br />-p TestPaths.py
+ <br /># Root of test tree
+ <br
/>D:\src\llvm\tools\lldb\packages\Python\lldbsuite\test
+ <br /># Required in order to be able to debug the test.
+ <br />--no-multiprocess
+ </code>
+ </li>
+ <li>
+ As copy-pastable command line:<br/>
+ <code>
+ -q --arch=i686 --executable
D:/src/llvmbuild/ninja/bin/lldb.exe -s D:/src/llvmbuild/ninja/lldb-test-traces
+ -u CXXFLAGS -u CFLAGS --enable-crash-dialog -C
d:\src\llvmbuild\ninja_release\bin\clang.exe
+ -p TestPaths.py
D:\src\llvm\tools\lldb\packages\Python\lldbsuite\test --no-multiprocess
+ </code>
+ </li>
+ </ul>
+ </li>
+ </ul>
</p>
</div>
<div class="postfooter"></div>
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
