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

Sublime​Anarchy​Debug

by dunkelstern ST3 OS XLinux

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

Labels debugger

Details

Installs

  • Total 291
  • Win 0
  • OS X 192
  • Linux 99
Jan 22 Jan 21 Jan 20 Jan 19 Jan 18 Jan 17 Jan 16 Jan 15 Jan 14 Jan 13 Jan 12 Jan 11 Jan 10 Jan 9 Jan 8 Jan 7 Jan 6 Jan 5 Jan 4 Jan 3 Jan 2 Jan 1 Dec 31 Dec 30 Dec 29 Dec 28 Dec 27 Dec 26 Dec 25 Dec 24 Dec 23 Dec 22 Dec 21 Dec 20 Dec 19 Dec 18 Dec 17 Dec 16 Dec 15 Dec 14 Dec 13 Dec 12 Dec 11 Dec 10 Dec 9 Dec 8
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
OS X 0 0 0 1 0 0 1 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 2 1 0 0 0 0 0 1 0 0 1 1 0 0 0 0 0 1
Linux 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 1

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:).