ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Sublime​Anarchy​Debug

by dunkelstern ST3 MacLinux

LLDB Integration for Sublime Text 3 (Breakpoints, LLDB console, Backtrace view)

Labels debugger

Details

Installs

  • Total 797
  • Win 1
  • Mac 501
  • Linux 295
Sep 19 Sep 18 Sep 17 Sep 16 Sep 15 Sep 14 Sep 13 Sep 12 Sep 11 Sep 10 Sep 9 Sep 8 Sep 7 Sep 6 Sep 5 Sep 4 Sep 3 Sep 2 Sep 1 Aug 31 Aug 30 Aug 29 Aug 28 Aug 27 Aug 26 Aug 25 Aug 24 Aug 23 Aug 22 Aug 21 Aug 20 Aug 19 Aug 18 Aug 17 Aug 16 Aug 15 Aug 14 Aug 13 Aug 12 Aug 11 Aug 10 Aug 9 Aug 8 Aug 7 Aug 6 Aug 5
Windows 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Mac 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 1 1
Linux 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

Sublime Text 3 plugin for LLDB integration

Features

  • Setting breakpoints
  • Running with connected stdin/out/err in output panel
  • LLDB debug prompt
  • Local variable display
  • Backtraces

Roadmap

  • Stabilize killing of debug server
  • Work out bugs in lldb console show/hide
  • Remote debugging

Setup

Use the default Sublime method of overriding configuration from the menu. Available configuration options:

  • lldb_python_path path to lldb python package directory to use for the debugger
  • auto_show_lldb_console boolean, automatically show the lldb console and backtrace windows when starting the debugger

How to use

To use the debugger you have to configure a debug target and its settings. To keep it with the project we save the settings to the sublime project file.

Example content of Project.sublime-project:

{
    "folders": [
        {
            "path": ".",
        }
    ]
    "settings": {
        "SublimeAnarchyDebug": {
            "debug": {
                "executable": "${project_path}/bin/executable",
                "params": [
                ],
                "path": [
                ],
                "environment": [
                ],
                "working_dir": "${project_path}"
            }
        }
    }
}

Put that into your project root and use the menu entry Project->Open Project... to open the project (or double-click in your filesystem browser or even open with subl <ProjectFile> from the command line.)

If the project is open just use the Command Palette to execute some Debug commands (all prefixed with AnarchyDebug:).