This is an archive of the discontinued LLVM Phabricator instance.

Differential D12668

[www] Typo fixes.
ClosedPublic

Authored by brucem on Sep 6 2015, 8:40 AM.

Details

Reviewers
clayborg
ki.stfu
Commits
rGb61f89ee52d9: [www] Typo fixes.
rLLDB246969: [www] Typo fixes.
rL246969: [www] Typo fixes.

Diff Detail

Repository
rL LLVM

Event Timeline

brucem updated this revision to Diff 34123.Sep 6 2015, 8:40 AM
brucem retitled this revision from to [www] Typo fixes..
brucem updated this object.
brucem added a reviewer: clayborg.
brucem added a subscriber: lldb-commits.
Herald added subscribers: srhines, danalbert, tberghammer. · View Herald TranscriptSep 6 2015, 8:40 AM
ki.stfu accepted this revision.Sep 7 2015, 5:35 AM
ki.stfu added a reviewer: ki.stfu.
This revision is now accepted and ready to land.Sep 7 2015, 5:35 AM
Closed by commit rL246969: [www] Typo fixes. (authored by brucem). · Explain WhySep 7 2015, 6:04 AM
This revision was automatically updated to reflect the committed changes.

Revision Contents

PathSize
lldb/
trunk/
www/
10 lines
2 lines
4 lines
2 lines

Diff 34153

lldb/trunk/www/build.html

Show All 10 Lines<body>
</div> </div>
<div id="container"> <div id="container">
<div id="content"> <div id="content">
<!--#include virtual="sidebar.incl"--> <!--#include virtual="sidebar.incl"-->
<div id="middle"> <div id="middle">
<h1 class="postheader">Continuous Integraton</h1> <h1 class="postheader">Continuous Integration</h1>
<div class="postcontent"> <div class="postcontent">
<p> <p>
The following LLVM buildbots build and test LLDB trunk: The following LLVM buildbots build and test LLDB trunk:
<ul> <ul>
<li> <a href="http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake">LLDB Ubuntu 14.04 x86_64 (CMake, clang-3.5+/gcc-4.8, i386/x86_64)</a> <li> <a href="http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake">LLDB Ubuntu 14.04 x86_64 (CMake, clang-3.5+/gcc-4.8, i386/x86_64)</a>
</li> </li>
<li> <a href="http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-android">LLDB Ubuntu 14.04 x86_64->Android (CMake, gcc-4.9 arm/arm64/x86)</a> <li> <a href="http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-android">LLDB Ubuntu 14.04 x86_64->Android (CMake, gcc-4.9 arm/arm64/x86)</a>
</li> </li>
▲ Show 20 Lines • Show All 329 Lines • ▼ Show 20 Lines <div id="content">
</p> </p>
<code>&gt; python -c 'import lldb'</code></p> <code>&gt; python -c 'import lldb'</code></p>
<h2 id="cross-compilation">Cross-compiling LLDB</h2> <h2 id="cross-compilation">Cross-compiling LLDB</h2>
<p> <p>
In order to debug remote targets running different architectures than your host, you In order to debug remote targets running different architectures than your host, you
will need to compile LLDB (or at least the server component) for the target. While will need to compile LLDB (or at least the server component) for the target. While
the easiest solution is to just compile it locally on the target, this is often not the easiest solution is to just compile it locally on the target, this is often not
feasable, and in these cases you will need to cross-compile LLDB on your host. feasible, and in these cases you will need to cross-compile LLDB on your host.
</p> </p>
<p> <p>
Cross-compilation is often a daunting task and has a lot of quirks which depend on Cross-compilation is often a daunting task and has a lot of quirks which depend on
the exact host and target architectures, so it is not possible to give a universal the exact host and target architectures, so it is not possible to give a universal
guide which will work on all platforms. However, here we try to provide an overview guide which will work on all platforms. However, here we try to provide an overview
of the cross-compilation process along with the main things you should look out for. of the cross-compilation process along with the main things you should look out for.
</p> </p>
▲ Show 20 Lines • Show All 74 Lines • ▼ Show 20 Lines <div id="content">
<p> <p>
You can of course also specify the usual cmake options like CMAKE_BUILD_TYPE, etc. You can of course also specify the usual cmake options like CMAKE_BUILD_TYPE, etc.
</p> </p>
<h3>Example 1: Cross-compiling for linux arm64 on Ubuntu host</h3> <h3>Example 1: Cross-compiling for linux arm64 on Ubuntu host</h3>
<p> <p>
Ubuntu already provides the packages necessary to cross-compile LLDB for arm64. It Ubuntu already provides the packages necessary to cross-compile LLDB for arm64. It
is sufficient to install pacakges gcc-aarch64-linux-gnu, g++-aarch64-linux-gnu, is sufficient to install packages gcc-aarch64-linux-gnu, g++-aarch64-linux-gnu,
binutils-aarch64-linux-gnu. Then it is possible to prepare the cmake build with the binutils-aarch64-linux-gnu. Then it is possible to prepare the cmake build with the
following parameters: following parameters:
</p> </p>
<code> <code>
-DCMAKE_CROSSCOMPILING=1 \<br/> -DCMAKE_CROSSCOMPILING=1 \<br/>
-DCMAKE_C_COMPILER=aarch64-linux-gnu-gcc \<br/> -DCMAKE_C_COMPILER=aarch64-linux-gnu-gcc \<br/>
-DCMAKE_CXX_COMPILER=aarch64-linux-gnu-g++ \<br/> -DCMAKE_CXX_COMPILER=aarch64-linux-gnu-g++ \<br/>
-DLLVM_HOST_TRIPLE=aarch64-unknown-linux-gnu \<br/> -DLLVM_HOST_TRIPLE=aarch64-unknown-linux-gnu \<br/>
Show All 15 Lines <div id="content">
-target aarch64-linux-gnu \<br/> -target aarch64-linux-gnu \<br/>
-I /usr/aarch64-linux-gnu/include/c++/4.8.2/aarch64-linux-gnu \<br/> -I /usr/aarch64-linux-gnu/include/c++/4.8.2/aarch64-linux-gnu \<br/>
-I /usr/aarch64-linux-gnu/include -I /usr/aarch64-linux-gnu/include
</code> </code>
<p> <p>
If you wanted to build a full version of LLDB and avoid passing If you wanted to build a full version of LLDB and avoid passing
-DLLDB_DISABLE_PYTHON and other options, you would need to obtain the target -DLLDB_DISABLE_PYTHON and other options, you would need to obtain the target
versions of the respective libraries. The easiest way to achive this is to use the versions of the respective libraries. The easiest way to achieve this is to use the
<code>qemu-debootstrap</code> utility, which can prepare a system image using qemu <code>qemu-debootstrap</code> utility, which can prepare a system image using qemu
and chroot to simulate the target environment. Then you can install the necessary and chroot to simulate the target environment. Then you can install the necessary
packages in this environment (python-dev, libedit-dev, etc.) and point your packages in this environment (python-dev, libedit-dev, etc.) and point your
compiler to use them using the correct -I and -L arguments. compiler to use them using the correct -I and -L arguments.
</p> </p>
<h3>Example 2: Cross-compiling for Android on Linux</h3> <h3>Example 2: Cross-compiling for Android on Linux</h3>
Show All 22 Lines <div id="content">
-DANDROID_TOOLCHAIN_DIR=$HOME/Toolchains/x86-android-toolchain \<br/> -DANDROID_TOOLCHAIN_DIR=$HOME/Toolchains/x86-android-toolchain \<br/>
-DANDROID_ABI=x86 \<br/> -DANDROID_ABI=x86 \<br/>
-DLLVM_HOST_TRIPLE=i386-unknown-linux-android \<br/> -DLLVM_HOST_TRIPLE=i386-unknown-linux-android \<br/>
-DLLVM_TABLEGEN=&lt;path-to-host&gt;/bin/llvm-tblgen \<br/> -DLLVM_TABLEGEN=&lt;path-to-host&gt;/bin/llvm-tblgen \<br/>
-DCLANG_TABLEGEN=&lt;path-to-host&gt;/bin/clang-tblgen -DCLANG_TABLEGEN=&lt;path-to-host&gt;/bin/clang-tblgen
</code> </code>
<p> <p>
Note that the full LLVM build is not functional on android yet, so simply runing Note that the full LLVM build is not functional on android yet, so simply running
<code>ninja</code> will not work. You will need to manually specify the target you <code>ninja</code> will not work. You will need to manually specify the target you
want to build: <code>lldb</code>, <code>lldb-server</code>, etc. want to build: <code>lldb</code>, <code>lldb-server</code>, etc.
</p> </p>
</div> </div>
<div class="postfooter"></div> <div class="postfooter"></div>
</div> </div>
</div> </div>
</div> </div>
</div> </div>
</body> </body>
</html> </html>

lldb/trunk/www/index.html

Show First 20 Lines • Show All 55 Lines • ▼ Show 20 Lines <div id="middle">
language features and runtimes in expressions without having to reimplement <b>any</b> language features and runtimes in expressions without having to reimplement <b>any</b>
of this functionality. It also leverages the compiler to take care of all ABI of this functionality. It also leverages the compiler to take care of all ABI
details when making functions calls for expressions, when disassembling details when making functions calls for expressions, when disassembling
instructions and extracting instruction details, and much more. instructions and extracting instruction details, and much more.
<p>The major benefits include:</p> <p>The major benefits include:</p>
<ul> <ul>
<li>Up to date language support for C, C++, Objective C</li> <li>Up to date language support for C, C++, Objective C</li>
<li>Multi-line expressions that can declare local variables and types</li> <li>Multi-line expressions that can declare local variables and types</li>
<li>Utilitize the JIT for expressions when supported</li> <li>Utilize the JIT for expressions when supported</li>
<li>Evaluate expression Intermediate Representation (IR) when JIT can't be used</li> <li>Evaluate expression Intermediate Representation (IR) when JIT can't be used</li>
</ul> </ul>
</div> </div>
</div> </div>
<div class="post"> <div class="post">
<h1 class ="postheader">Reusability</h1> <h1 class ="postheader">Reusability</h1>
<div class="postcontent"> <div class="postcontent">
▲ Show 20 Lines • Show All 63 Lines • Show Last 20 Lines

lldb/trunk/www/test.html

Show First 20 Lines • Show All 75 Lines • ▼ Show 20 Lines <div id="content">
The default value is the number of CPU cores on your The default value is the number of CPU cores on your
system. system.
</p> </p>
<p> <p>
The parallel test running feature will handle an The parallel test running feature will handle an
additional <code>--test-subdir SUBDIR</code> arg. When additional <code>--test-subdir SUBDIR</code> arg. When
specified, SUBDIR is relative to the root test directory specified, SUBDIR is relative to the root test directory
and will limit all parallel test running to that and will limit all parallel test running to that
sudirectory's tree of tests. subdirectory's tree of tests.
</p> </p>
<p> <p>
The parallel test runner will run all tests within a The parallel test runner will run all tests within a
given directory serially, but will run multiple given directory serially, but will run multiple
directories concurrently. Thus, as a test writer, we directories concurrently. Thus, as a test writer, we
provide serialized test run semantics within a provide serialized test run semantics within a
directory. Note child directories are considered directory. Note child directories are considered
entirely separate, so two child directories could be entirely separate, so two child directories could be
Show All 19 Lines <div id="content">
parameters correspond to the <code>platform select</code> and <code>platform parameters correspond to the <code>platform select</code> and <code>platform
connect</code> LLDB commands. You will usually also need to specify the compiler and connect</code> LLDB commands. You will usually also need to specify the compiler and
architecture for the remote system. architecture for the remote system.
</li> </li>
</ul> </ul>
<p> <p>
Currently, running the remote test suite is supported only with Currently, running the remote test suite is supported only with
<code>dotest.py</code> (or <code>dosep.py</code> with a single thread), but we <code>dotest.py</code> (or <code>dosep.py</code> with a single thread), but we
expect this issue to be adressed in the near future. expect this issue to be addressed in the near future.
</p> </p>
</div> </div>
<div class="postfooter"></div> <div class="postfooter"></div>
</div> </div>
</div> </div>
</div> </div>
</div> </div>
</body> </body>
</html> </html>

lldb/trunk/www/varformats.html

Show First 20 Lines • Show All 984 Lines • ▼ Show 20 Lines compliant implementation.
</td> </td>
<table> <table>
<code> <b>(lldb)</b> frame variable one<br> <code> <b>(lldb)</b> frame variable one<br>
(i_am_cool) one = int = 3, float = 3.14159, char = 69<br> (i_am_cool) one = int = 3, float = 3.14159, char = 69<br>
<b>(lldb)</b> frame variable one --summary NamedSummary<br> <b>(lldb)</b> frame variable one --summary NamedSummary<br>
(i_am_cool) one = x=3<br> (i_am_cool) one = x=3<br>
</code> </p> </code> </p>
<p>When defining a named summmary, binding it to one or more types becomes optional. <p>When defining a named summary, binding it to one or more types becomes optional.
Even if you bind the named summary to a type, and later change the summary string Even if you bind the named summary to a type, and later change the summary string
for that type, the named summary will not be changed by that. You can delete for that type, the named summary will not be changed by that. You can delete
named summaries by using the <code>type summary delete</code> command, as if the named summaries by using the <code>type summary delete</code> command, as if the
summary name was the datatype that the summary is applied to</p> summary name was the datatype that the summary is applied to</p>
<p>A summary attached to a variable using the </code>--summary</code> option, <p>A summary attached to a variable using the </code>--summary</code> option,
has the same semantics that a custom format attached using the <code>-f</code> has the same semantics that a custom format attached using the <code>-f</code>
option has: it stays attached till you attach a new one, or till you let option has: it stays attached till you attach a new one, or till you let
▲ Show 20 Lines • Show All 330 Lines • Show Last 20 Lines