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 377
  • Win 0
  • OS X 249
  • Linux 128
Jul 21 Jul 20 Jul 19 Jul 18 Jul 17 Jul 16 Jul 15 Jul 14 Jul 13 Jul 12 Jul 11 Jul 10 Jul 9 Jul 8 Jul 7 Jul 6 Jul 5 Jul 4 Jul 3 Jul 2 Jul 1 Jun 30 Jun 29 Jun 28 Jun 27 Jun 26 Jun 25 Jun 24 Jun 23 Jun 22 Jun 21 Jun 20 Jun 19 Jun 18 Jun 17 Jun 16 Jun 15 Jun 14 Jun 13 Jun 12 Jun 11 Jun 10 Jun 9 Jun 8 Jun 7
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
OS X 0 0 1 1 0 0 0 0 0 0 1 2 0 0 0 0 1 0 2 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 1 1 0 0 0 1 0 1 0 0 0
Linux 0 0 0 1 1 0 1 1 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

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