diff options
author | Greg Clayton <gclayton@apple.com> | 2010-06-10 02:48:13 +0000 |
---|---|---|
committer | Greg Clayton <gclayton@apple.com> | 2010-06-10 02:48:13 +0000 |
commit | c3df2321646bd8bb0b6600c23fe60ea85f9b8d9a (patch) | |
tree | 7c3a1b63b8fc5d80ffaa04bb253e5440d094a51f | |
parent | 5f2adccc1b61998109862a86f119afaf13994589 (diff) | |
download | bcm5719-llvm-c3df2321646bd8bb0b6600c23fe60ea85f9b8d9a.tar.gz bcm5719-llvm-c3df2321646bd8bb0b6600c23fe60ea85f9b8d9a.zip |
Removing www files, will replace them with new ones after this commit.
llvm-svn: 105777
-rw-r--r-- | lldb/www/content.css | 25 | ||||
-rw-r--r-- | lldb/www/index.html | 197 | ||||
-rw-r--r-- | lldb/www/menu.css | 39 | ||||
-rw-r--r-- | lldb/www/menu.html.incl | 20 |
4 files changed, 0 insertions, 281 deletions
diff --git a/lldb/www/content.css b/lldb/www/content.css deleted file mode 100644 index ab6983b4849..00000000000 --- a/lldb/www/content.css +++ /dev/null @@ -1,25 +0,0 @@ -html, body { - padding:0px; - font-size:small; font-family:"Lucida Grande", "Lucida Sans Unicode", Arial, Verdana, Helvetica, sans-serif; background-color: #fff; color: #222; - line-height:1.5; -} - -h1, h2, h3, tt { color: #000 } - -h1 { padding-top:0px; margin-top:0px;} -h2 { color:#333333; padding-top:0.5em; } -h3 { padding-top: 0.5em; margin-bottom: -0.25em; color:#2d58b7} -li { padding-bottom: 0.5em; } -ul { padding-left:1.5em; } - -/* Slides */ -IMG.img_slide { - display: block; - margin-left: auto; - margin-right: auto -} - -.itemTitle { color:#2d58b7 } - -/* Tables */ -tr { vertical-align:top } diff --git a/lldb/www/index.html b/lldb/www/index.html deleted file mode 100644 index 35e05611610..00000000000 --- a/lldb/www/index.html +++ /dev/null @@ -1,197 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" - "http://www.w3.org/TR/html4/strict.dtd"> -<!-- Material used from: HTML 4.01 specs: http://www.w3.org/TR/html401/ --> -<html> -<head> - <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> - <title>The LLDB Debugger</title> - <link type="text/css" rel="stylesheet" href="menu.css"> - <link type="text/css" rel="stylesheet" href="content.css"> -</head> - -<body> -<!--#include virtual="menu.html.incl"--> -<div id="content"> - <!--*********************************************************************--> - <h1>The LLDB Debugger</h1> - <!--*********************************************************************--> - - <p>LLDB is a next generation, high-performance debugger. It is built as a set - of reusable components which highly leverage existing libraries in the - larger LLVM Project, such as the Clang expression parser and LLVM - disassembler.</p> - <p>LLDB is in early development, but is mature enough to support basic - debugging scenarios on Mac OS X in C, Objective-C and C++.</p> - - <p>All of the code in the LLDB project is available under the standard - <a href="http://llvm.org/docs/DeveloperPolicy.html#license">LLVM - License</a>, an open source "BSD-style" license.</p> - - <!--=====================================================================--> - <h2 id="goals">Goals</h2> - <!--=====================================================================--> - - <p>The current state of the art in open source debuggers are that - they work in the common cases for C applications, but don't - handle many "hard cases" properly. For example, C++ expression - parsing, handling overloading, templates, multi-threading, and - other non-trivial scenarios all work in some base cases, but - don't work reliably.</p> - - <p>The goal of LLDB is to provide an amazing debugging experience that "just - works". We aim to solve these long-standing problems where debuggers get - confused, so that you can think about debugging your problem, not - about deficiencies in the debugger.</p> - - <p>With a long view, there is no good reason for a debugger to - reinvent its own C/C++ parser, type system, know all the - target calling convention details, implement its own disassembler, - etc. By using the existing libraries vended by the LLVM - project, we believe that many of these problems will be defined - away, and the debugger can focus on important issues like - process control, efficient symbol reading and indexing, thread - management, and other debugger-specific problems.</p> - - <p>Some more specific goals include:</p> - - <ul> - <li>Build libraries for inclusion in IDEs, command line tools, and - other analysis tools</li> - <li>High performance and efficient memory use</li> - <li>Extensible: Python scriptable and use a plug-in architecture</li> - <li>Reuse existing compiler technology where it makes sense</li> - <li>Excellent multi-threaded debugging support</li> - <li>Great support for C, Objective-C and C++</li> - <li>Retargetable to support multiple platforms</li> - <li>Provide a base for debugger research and other innovation</li> - </ul> - - <!--=====================================================================--> - <h2 id="why">Why a new debugger?</h2> - <!--=====================================================================--> - - <p>In order to achieve our goals we decided to start with a fresh architecture - that would support modern multi-threaded programs, handle debugging symbols - in an efficient manner, use compiler based code knowledge and have plug-in - support for functionality and extensions. Additionally we want the debugger - capabilities to be available to other analysis tools, be they scripts or - compiled programs, without requiring them to be GPL.</p> - - <!--=====================================================================--> - <h2 id="features">Features</h2> - <!--=====================================================================--> - - <p>LLDB supports a broad variety of basic debugging features such as - reading DWARF, supporting step, next, finish, backtraces, etc. Some - more interested bits are:</p> - - <ul> - <li>Plug-in architecture for portability and extensibility: - <ul> - <li>Object file parsers for executable file formats. Support currently - includes Mach-O (32 and 64-bit) & ELF (32-bit).</li> - <li>Object container parsers to extract object files contained within a file. - Support currently includes universal Mach-O files & BSD Archives. - </li> - <li>Debug symbol file parsers to incrementally extract debug information from - object files. Support currently includes DWARF & Mach-O symbol - tables.</li> - <li>Symbol vendor plug-ins collect data from a variety of different sources - for an executable object.</li> - <li>Disassembly plug-ins for each architecture. Support currently includes - an LLVM disassembler for <a - href="http://blog.llvm.org/2010/01/x86-disassembler.html">i386, - x86-64</a>, & ARM/Thumb.</li> - <li>Debugger plug-ins implement the host and target specific functions - required to debug.</li> - </ul> - <li>SWIG-generated script bridging allows Python to access and control the - public API of the debugger library.</li> - <li>A remote protocol server, debugserver, implements Mac OS X debugging on - i386 and x86-64.</li> - <li>A command line debugger - the lldb executable itself.</li> - <li>A framework API to the library.</li> - </ul> - - <!--=====================================================================--> - <h2 id="requirements">Platform Support</h2> - <!--=====================================================================--> - - <p>LLDB is known to work on the following platforms, but ports to new - platforms are welcome:</p> - - <li>Machine Architectures: - <ul> - <li>Mac OS X i386 and x86-64</li> - </ul></li> - - <!--=====================================================================--> - <h2 id="status">Current Status</h2> - <!--=====================================================================--> - - <p>LLDB is in early development and supports basic debugging scenarios on - Mac OS X. The public API has not been finalized, and different parts are - at different levels of maturity. We welcome any help fleshing out missing - pieces and improving the code.</p> - - <p>What works well:</p> - <ul> - <li>Process control, including external process control via debugserver - (which is included as part of the lldb project)</li> - <li>Breakpoints: Source-line, symbolic, C++ mangled names, module - scoping</li> - <li>Symbol reading and object file introspection</li> - <li>Script bridging</li> - <li>Thread inspection and stepping</li> - <li>Disassembly of i386, x86-64, & ARM/Thumb machine code, and - backtracing on i386 & x86-64</li> - <li>The basic command line prompt system, shared library tracking, - source listings.</li> - </ul> - - <p>What is still pretty new:</p> - <ul> - <li>The public API to the library</li> - <li>Expression evaluation</li> - <li>Objective-C support: stepping into/over, printing the description of - an object ("po")</li> - <li>Breakpoint actions & scripts</li> - <li>Attaching to existing processes</li> - </ul> - - <p>What isn't there yet:</p> - <ul> - <li>Regression test suite</li> - <li>Operating system support hasn't been fully modularized yet</li> - <li><a href="http://clang.llvm.org/docs/LanguageExtensions.html#blocks">Blocks</a> support</li> - <li>Calling functions in expressions</li> - <li>Objective-C 2.0 Support: Printing properties, synthetic properties, - Objective-C expressions, KVO, dynamic types, dot syntax, runtime data</li> - <li>C++ support: Method access, handling demangled names, dynamic types</li> - <li>Exception support: Breaking by name, thrown object, thrower</li> -</li> - </ul> - - <!--=====================================================================--> - <h2>Get it and get involved!</h2> - <!--=====================================================================--> - - <p>To check out the code, use:</p> - - <ul> - <li>svn co http://llvm.org/svn/llvm-project/lldb/trunk lldb</li> - </ul> - - <p>Note that LLDB currently only builds out of the box on Mac OS X with - Xcode, but patches to improve portability are definitely welcome.</p> - - <p>Discussions about LLDB should go to the <a - href="http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev">lldb-dev</a> mailing - list. Commit messages for the lldb SVN module are automatically sent to the - <a - href="http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits">lldb-commits</a> - mailing list, and this is also the preferred mailing list for patch - submissions.</p> -</div> -</body> -</html> diff --git a/lldb/www/menu.css b/lldb/www/menu.css deleted file mode 100644 index 6e96a457ab5..00000000000 --- a/lldb/www/menu.css +++ /dev/null @@ -1,39 +0,0 @@ -/***************/ -/* page layout */ -/***************/ - -[id=menu] { - position:fixed; - width:25ex; -} -[id=content] { - /* ***** EDIT THIS VALUE IF CONTENT OVERLAPS MENU ***** */ - position:absolute; - left:29ex; - padding-right:4ex; -} - -/**************/ -/* menu style */ -/**************/ - -#menu .submenu { - padding-top:1em; - display:block; -} - -#menu label { - display:block; - font-weight: bold; - text-align: center; - background-color: rgb(192,192,192); -} -#menu a { - padding:0 .2em; - display:block; - text-align: center; - background-color: rgb(235,235,235); -} -#menu a:visited { - color:rgb(100,50,100); -}
\ No newline at end of file diff --git a/lldb/www/menu.html.incl b/lldb/www/menu.html.incl deleted file mode 100644 index ed104c0c30a..00000000000 --- a/lldb/www/menu.html.incl +++ /dev/null @@ -1,20 +0,0 @@ -<div id="menu"> - <div> - <a href="http://llvm.org/">LLVM Home</a> - </div> - - <div class="submenu"> - <label>LLDB Info</label> - <a href="/index.html">About</a> - </div> - - <div class="submenu"> - <label>Quick Links</label> - <a href="http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev">lldb-dev</a> - <a href="http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits">lldb-commits</a> - <a href="http://llvm.org/bugs/">Bug Reports</a> - <a href="http://llvm.org/svn/llvm-project/lldb/trunk/">Browse SVN</a> - <a href="http://llvm.org/viewvc/llvm-project/lldb/trunk/">Browse ViewVC</a> - </div> -</div> - |