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

Xdebug Client

by martomo ST2/ST3

Xdebug debugger client for Sublime Text 2 and 3

Labels php, xdebug


  • 2014.
  • github.​com
  • github.​com
  • 3 years ago
  • 1 hour ago
  • 4 years ago


  • Total 78K
  • Win 40K
  • OS X 21K
  • Linux 18K
Apr 23 Apr 22 Apr 21 Apr 20 Apr 19 Apr 18 Apr 17 Apr 16 Apr 15 Apr 14 Apr 13 Apr 12 Apr 11 Apr 10 Apr 9 Apr 8 Apr 7 Apr 6 Apr 5 Apr 4 Apr 3 Apr 2 Apr 1 Mar 31 Mar 30 Mar 29 Mar 28 Mar 27 Mar 26 Mar 25 Mar 24 Mar 23 Mar 22 Mar 21 Mar 20 Mar 19 Mar 18 Mar 17 Mar 16 Mar 15 Mar 14 Mar 13 Mar 12 Mar 11 Mar 10 Mar 9
Windows 30 33 57 63 48 58 63 35 39 48 58 64 50 50 34 53 41 65 63 46 38 26 36 50 75 65 88 57 26 47 52 91 58 64 57 26 34 75 95 51 83 58 33 27 72 98
OS X 6 2 21 18 21 15 16 5 8 12 17 20 32 13 10 6 27 24 21 24 21 12 9 25 27 19 24 23 12 10 19 32 35 28 19 10 11 25 31 27 24 28 7 11 17 31
Linux 7 8 28 20 19 16 20 9 11 9 19 23 19 16 6 13 24 46 16 26 20 8 11 26 24 21 23 18 8 18 25 23 23 21 18 9 10 26 18 28 20 18 13 12 15 24




Xdebug debugger client integration for Sublime Text.


Based on the Xdebug protocol functionality in SublimeXdebug package by Kindari.



  • Remote debugging by configuring path mapping
  • Navigate on breakpoint hit to relevant file on specific line, when found on local drive
  • Customizable debugging layout for displaying stack history and context variables with syntax
  • Overview of breakpoints in all files and disable/enable breakpoints with simple click
  • Evaluate code within the current execution context, by setting watch expressions
  • Inspect (nested) context variables
  • Works on both Sublime Text 2 and 3


Here is a complete list of commands you can find Command Pallette under the Xdebug namespace or in the menu under Tools / Xdebug:

Start/Stop debugging session

  • Start Debugging - Ctrl+Shift+F9 or ⌘+Shift+F9
  • Start Debugging (Launch Browser)
  • Restart Session
  • Stop Debugging - Ctrl+Shift+F10 or ⌘+Shift+F10
  • Stop Debugging (Launch Browser)
  • Stop Debugging (Close Windows)

Launch Browser menu option will only show if you have an url configured within settings.


  • Add/Remove Breakpoint - Ctrl+F8 or ⌘+F8
  • Set Conditional Breakpoint - Shift+F8
  • Clear Breakpoints
  • Clear All Breakpoints

Watch expressions

  • Set Watch Expression
  • Edit Watch Expression
  • Remove Watch Expression
  • Clear Watch Expressions

Session commands

  • Evaluate
  • Execute
  • Status

Continuation commands

  • Run - Ctrl+Shift+F5 or ⌘+Shift+F5
  • Run To Line
  • Step Over - Ctrl+Shift+F6 or ⌘+Shift+F6
  • Step Into - Ctrl+Shift+F7 or ⌘+Shift+F7
  • Step Out - Ctrl+Shift+F8 or ⌘+Shift+F8
  • Stop
  • Detach


  • Restore Layout / Close Windows - Ctrl+Shift+F11 or ⌘+Shift+F11
  • Settings - Default
  • Settings - User


Package Control

Execute “Package Control: Install Package” in the Command Pallette to retrieve a list of available packages. Search in the list and install package Xdebug Client.


Clone the repository by executing the following command in your Packages directory:

git clone https://github.com/martomo/SublimeTextXdebug.git "Xdebug Client"


Get the latest source from GitHub and extract the source into your Packages directory.

Note: You can locate your Packages directory in the menu under Preferences / Browse Packages...


In order to be able to debug your PHP scripts, you will need have Xdebug extension installed on your server. See here for installation instructions

Below is a configuration template for php.ini/xdebug.ini, be warned if you are on a Live environment, remote_connect_back allows every debug request from any source to be accepted.

zend_extension = /absolute/path/to/your/xdebug-extension.so
;zend_extension = "C:\Program Files (x86)\PHP\ext\php_xdebug.dll"
xdebug.remote_enable = 1
xdebug.remote_host = ""
xdebug.remote_port = 9000
xdebug.remote_handler = "dbgp"
xdebug.remote_mode = req
xdebug.remote_connect_back = 1

For details about all available settings for configuring Xdebug, see here.


The following settings can be configured in Xdebug.sublime-settings or in *.sublime-project files:

For remote debugging to resolve the file locations it is required to configure the path mapping with the server path as key and local path as value.

Determine which URL to launch in the default web browser when starting/stopping a session.

An IDE key is used to identify with debugger engine when Sublime Text will start or stop a debugging session.

This package does not filter sessions by IDE key, it will accept any IDE key, also ones that do not match this configured IDE key. It is merely used when launching the default web browser with the configured URL.

Which port number Sublime Text should listen to connect with debugger engine.

Show super globals in context view.

Maximum amount of array children and object's properties to return.

Maximum amount of variable data to initially retrieve.

Maximum amount of nested levels to retrieve of array elements and object properties.

Break at first line on session start, when debugger engine has connected.

Break on exceptions, suspend execution when the exception name matches an entry in this list value.

Always close debug windows and restore layout on session stop.

Do not show possible password values in context output.

Show in output parsed response instead of raw XML.

Always launch browser on session start/stop.

This will only work if you have the 'url' setting configured.

When launching browser on session stop do not execute script.

Do not use the debugging window layout.

Window layout that is being used when debugging.

Group and index positions for debug views.

Custom gutter icons for indicating current line or enabled/disabled breakpoints.

Do not use same icon for above values, because Sublime Text is unable to use the same icon for different scopes, in case there are duplicate icons detected it will fall back to the corresponding icon in the package.

Path to Python installation on your system.
Which is being used to load missing modules.

Show detailed log information about communication between debugger engine and Sublime Text.

Below are examples how to configure your Xdebug.sublime-settings and *.sublime-project files.

Xdebug.sublime-settings “json { "path_mapping”: { “/absolute/path/to/file/on/server” : “/absolute/path/to/file/on/computer”, “/var/www/htdocs/example/” : “C:/git/websites/example/” }, “url”: “http://your.web.server/index.php”, “super_globals”: true, “close_on_stop”: true }

            "path": "..."
        "xdebug": {
            "path_mapping": {
                "/absolute/path/to/file/on/server" : "/absolute/path/to/file/on/computer",
                "/var/www/htdocs/example/" : "C:/git/websites/example/"
            "url": "http://your.web.server/index.php",
            "super_globals": true,
            "close_on_stop": true


Can I have both SublimeTextXdebug and SublimeXdebug installed?

No. Having installed both packages can cause conflicts, because they might both listen to the same port for a debugger engine response and have similar keymapping.

However (project) settings from SublimeXdebug are compatible with SublimeTextXdebug.

How can I start a debugging session?

SublimeTextXdebug can start or stop a debugging session by launching the default web browser with the configured URL and parameter XDEBUG_SESSION_START or XDEBUG_SESSION_STOP which uses the configured IDE key as value. By default the IDE key is sublime.xdebug.

When you do not configure the URL, the plugin will still listen for debugging connections from Xdebug, but you will need to trigger Xdebug for a remote session.

If you want to run a start a debugging session from command line, before you run your script, you will need to set the environment variable XDEBUG_CONFIG with the IDE key.

Windows “ set XDEBUG_CONFIG="idekey=sublime.xdebug” php myscript.php


export XDEBUG_CONFIG=“idekey=sublime.xdebug” php myscript.php

Make sure before defining the environment variable you have switched to the proper user environment.  
As example you would set the environment variable as __guest__ and execute the script as __root__ _(sudo)_, then __root__ will not have the environment variable XDEBUG_CONFIG that was defined by __guest__.

#### How do I set a breakpoint and/or watch expression?
With SublimeTextXdebug you can easily [add/remove breakpoints](#breakpoints), which are send on session start.  
Or [set/edit/remove watch expressions](#watch-expressions), that are evaluated in the current execution context.  

Setting a conditional breakpoints or watch expressions is quite easy, it is like an __if__ statement in PHP.

As example you only want to stop on breakpoint when value of __$number__ is equal to __13__, then your __Breakpoint condition__ would be `$number==13`.  
Another example would be when you would like to know the value of __$item['image']__ on each break, then your __Watch expression__ would be `$item['image']`.

Another way is to set the breakpoint in your PHP code with the following function [`xdebug_break()`](http://xdebug.org/docs/remote#xdebug_break).

#### How to configure or disable breaking on exceptions?
By default the execution of a debugging session is suspended on each of the following exception names:
- __"Catchable fatal error"__ - E_RECOVERABLE_ERROR (since PHP 5.2.0)
- __"Parse error"__ - E_PARSE
- __"Notice"__ - E_NOTICE, E_USER_NOTICE
- __"Strict standards"__ - E_STRICT
- __"Deprecated"__ - E_DEPRECATED, E_USER_DEPRECATED (since PHP 5.3.0)
- __"Xdebug"__
- __"Unknown error"__

In order to specify which exception names to suspend the execution of a debugging session, configure the `break_on_exception` setting with a list of the specific exception names by choice from the list shown above.  

It is also possible to specify custom exceptions instead of __all__ exceptions (__"Fatal error"__). For example if you would configure __"MissingArgumentException"__ instead of __"Fatal error"__, it would not break on __"InvalidParameterException"__.

To disable breaking on exceptions either configure an empty list `break_on_exception: []` or set as `break_on_exception: false`.

#### How can I customize/disable the debugging layout?
Re-adjust the layout in Sublime Text to your liking and then in console (<kbd>Ctrl+\`</kbd>) you type `window.get_layout()` and set that value as your `debug_layout`.

Further customizing can be done by assigning the Xdebug views to a group/index with the `breakpoint_group`, `breakpoint_index`, `context_group`, `context_index`, `stack_group`, `stack_index`, `watch_group`, `watch_index` settings.

Or you can disable the debugging layout by setting `disable_layout: true`, which will open all Xdebug views in current active group/window on session start and does not change your layout.

#### How to solve `ImportError`?
Older versions of Sublime Text do not come with Python bundled and rely on your Python system installation.  
Some systems do not include specific modules which are required by this package, such as __pyexpat__.

Configure the `python_path` setting to the path of your Python installation on your system which is either newer or has all required modules. For example: `"python_path" : "/usr/lib/python2.7"`.

#### What to do when you experience any issues?
First check following _possible_ solutions that could resolve any issues:

- Use __absolute__ paths in your `path_mapping` setting, Xdebug does not return symbolic links.
- Breakpoint is on an empty line, Xdebug does not stop on empty lines.
- Set `port` and [xdebug.remote_port](http://xdebug.org/docs/all_settings#remote_port) to different port *(9001)*, default port 9000 might already be used by an other application.
- Add an exception for Sublime Text *(plugin_host.exe)* to your firewall, response from Xdebug could be blocked by firewall.
- Lower the `max_data`/`max_depth`/`max_children` settings to increase response speed or prevent crashing, Xdebug could return to much data to process.
- Change permissions for Sublime Text and it's packages on your filesystem, Sublime Text or package might not have valid rights.

Do you still experience any issues, then [create an issue](https://github.com/martomo/SublimeTextXdebug/issues/new) including the following data:

- What operation system(s) and version of Sublime Text are you using?
- How did you [install](https://github.com/martomo/SublimeTextXdebug#installation) SublimeTextXdebug, Package Control, git clone or download?
- Are you trying to debug the script remotely or locally, through browser or command line?
- Which version of Xdebug extension do you have?
- Can you post your [project/settings file](https://github.com/martomo/SublimeTextXdebug#configuration) and [Xdebug configuration](https://github.com/martomo/SublimeTextXdebug#xdebug) from the *.ini located on your server.
- Does the console window (<kbd>Ctrl+\`</kbd>) show any more information regarding the error?

## License

SublimeTextXdebug is released under the [MIT License](http://www.opensource.org/licenses/MIT).