Google Git
Sign in
fuchsia / third_party / swift-lldb / refs/tags/swift-4.0-DEVELOPMENT-SNAPSHOT-2017-11-08-a
tagfab39ab2a10fbb64ecd59281fb4deceb06b78015
taggerSwift Jenkins <swift_jenkins@apple.com>Wed Nov 08 19:10:30 2017 -0600
object35373a0918c9ec61a300868ab4f9337ebf338f95 
Tag build swift-4.0-DEVELOPMENT-SNAPSHOT-2017-11-08-a
commit35373a0918c9ec61a300868ab4f9337ebf338f95[log] [tgz]
authorKuba (Brecka) Mracek <mracek@apple.com>Wed Aug 23 11:42:20 2017 -0700
committerGitHub <noreply@github.com>Wed Aug 23 11:42:20 2017 -0700
treedf43205a73c71df3c63523c42a988cfe539030f5
parent70491313e5e2769ac79262a42062c85c05948905 [diff]
[lldb] Correctly escape newlines and backslashes in the JSON serializer (#248)

JSON serializer fails to escape newlines and backslashes. Let's fix that.
4 files changed
tree: df43205a73c71df3c63523c42a988cfe539030f5
  1. cmake/
  2. docs/
  3. examples/
  4. include/
  5. lit/
  6. lldb.xcodeproj/
  7. lldb.xcworkspace/
  8. packages/
  9. resources/
  10. scripts/
  11. source/
  12. test/
  13. third_party/
  14. tools/
  15. unittests/
  16. utils/
  17. www/
  18. .arcconfig
  19. .clang-format
  20. .gitignore
  21. CMakeLists.txt
  22. CODE_OWNERS.txt
  23. CONTRIBUTING.md
  24. EXPORT.APPLE
  25. INSTALL.txt
  26. LICENSE.TXT
  27. notifications.json
  28. README.md
  29. use_lldb_suite_root.py
README.md

Swift Debugger and REPL

Status
macOSBuild Status
Ubuntu 14.04Build Status
Ubuntu 15.10Build Status

Welcome to the Swift Debugger and REPL!

Swift is a new, high performance systems programming language. It has a clean and modern syntax, offers seamless access to existing C and Objective-C code and frameworks, and is memory safe (by default).

This repository covers the Swift Debugger and REPL support, built on top of the LLDB Debugger.

Building LLDB for Swift

To build LLDB for Swift, you must have the following prerequisites installed on your development system:

  • OS X Requirements

  • Linux x86_64 (Ubuntu 14.04, Ubuntu 15.10)

    • Clang 3.5 or later.

    • Cmake (version 2.8.12.2 or later)

    • Python 2.7

Once the pre-requisites are satisfied, follow these steps from a bash-like shell:

mkdir myswift
cd myswift
git clone https://github.com/apple/swift-lldb.git lldb
lldb/scripts/build-swift-cmake.py --test

The lldb build script will clone additional repositories for required dependencies if they are not already present. An optional --update argument can be used to refresh these required repositories. Products of the build process will be placed in the build/ directory under the root source directory.

Inter-project Directory Layout

LLDB for Swift introduces new dependencies that do not exist with core LLDB. In particular, LLDB for Swift makes extensive use of the Swift codebase.

Each one of the directories listed below underneath the overall source_root are backed by a Swift.org repository:

.
+-- clang/
|
+-- cmark/
|
+-- lldb/
|
+-- llvm/
|
+-- ninja/
|
+-- swift/

Details on the contents:

  • clang

    Contains the stable version of Clang used by Swift.

  • cmark

    Contains markdown support used by Swift.

  • lldb

    Contains the LLDB source that includes Swift support. All of LLDB for Swift is contained in this repository. Core LLDB contents are merged into this repository. No other copy of LLDB source code is required.

  • llvm

    Contains the stable version of LLVM used by Swift.

  • ninja

    Contains the Ninja build system.

  • swift

    Contains the Swift Language and Swift Runtime code.

Note: If you don‘t use the build-swift-cmake.py script to do the initial clone of the related project repositories, you’ll need to manually clone them to the names above:

Contribution Subtleties

The swift-lldb project enhances the core LLDB project developed under the LLVM Project. Swift support in the debugger is added via the existing source-level plugin infrastructure, isolated to files that are newly introduced in the lldb-swift repository.

Files that come from the core LLDB project can be readily identified by their use of the LLVM comment header. As no local changes should be made to any of these files, follow the standard guidance for upstream changes.