Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
---|---|---|---|---|---|---|---|---|---|---|
Sublimetextxdebug | 565 | 4 years ago | 69 | mit | Python | |||||
Xdebug debugger client for Sublime Text 2 and 3 | ||||||||||
Sublime_debugger | 436 | 7 years ago | 24 | apache-2.0 | Python | |||||
Interactive debugger for sublime | ||||||||||
Jsdebuggr | 146 | 6 years ago | 10 | Python | ||||||
Add, remove, enable, and disable breakpoints in javascript from the comfort of Sublime Text :D | ||||||||||
Coronasdk Sublimetext | 104 | 2 years ago | 2 | mit | Python | |||||
Corona Editor is the official Corona SDK plugin for Sublime Text | ||||||||||
Sublimedebugger | 46 | 5 years ago | 17 | mit | Python | |||||
Graphical Debugger for Sublime Text | ||||||||||
Pythonbreakpoints | 30 | 6 years ago | 5 | Python | ||||||
Sublime Text plugin to set Python breakpoints | ||||||||||
Subdebug | 27 | 9 years ago | 7 | mit | Python | |||||
A debugging plugin for Sublime that communicates with MobDebug (https://github.com/pkulchenko/MobDebug). | ||||||||||
Sublimelldb | 26 | 7 years ago | 1 | other | Python | |||||
ABANDONED. I'm not using nor working on this any more. A plugin to debug programs in Sublime Text 2 using the LLDB debugger. (Let me know if you want to take ownership) | ||||||||||
Sublimeanarchydebug | 8 | 7 years ago | 7 | Python | ||||||
LLDB Integration for Sublime Text 3 (Breakpoints, LLDB console, Backtrace view) | ||||||||||
Stdi | 4 | 11 years ago | other | Python | ||||||
Sublime Text 2 Debugger Interface |
A debugger plugin for interactive ruby and RoR debugging on Sublime Text.
By Shuky chen, based on the Debugger and Byebug gems.
In order to start debugging ruby or RoR applications all you need to do is to install Debugger plugin and press on F6 or Shift+F6 or Alt+Shift+F6
Here is a complete list of commands you can find Command Pallette under the Debugger
namespace or in the menu under Tools / Debugger
:
Sublime Debugger relies on two seperate gems for diffirent ruby versions. For Ruby 1.9.3 you need the debugger gem, which can be installed using gem install debugger
, and for Ruby 2.0.0 you need the byebug gem, which can be installed using gem install byebug
.
I cannot test this against all ruby versions, so I only explicity support Ruby 1.9.3 and Ruby 2.0.0. RVM is a good way to have multiple ruby versions installed at once and switch between them when debugging or running normally. Sublime Debugger will use the ruby version that you set as default, so you must set either Ruby 1.9.3 or Ruby 2.0.0 as the default. Remember to reinstall the byebug or debugger gem when you change ruby versions, or else you will get an Connection could not be made: [Errno ##] Connection refused
error.
If you need to have your ruby program running with an unspported ruby version you can manually add the version to the supported versions list. In the package's directory, which you can get to by going to preferences -> browse packages
in sublime text and then opening the Ruby Debugger
folder, there is a ruby_version_discoverer.rb
file where you can add your ruby version.
Execute "Package Control: Install Package" in the Command Pallette to retrieve a list of available packages.
Search in the list and install package Ruby Debugger
.
Clone the repository by executing the following command in your Packages directory:
git clone https://github.com/shuky19/sublime_debugger.git "Ruby Debugger"
Get the latest source from GitHub and extract the source into your Packages directory to a folder named "Ruby Debugger".
Note: You can locate your Packages directory in the menu under Preferences / Browse Packages...
Connection could not be made: [Errno 61] Connection refused
in the output window?Well, Most of the reasons for this error come from environmental problems, following the steps below will help you fix it:
which ruby
and ruby --version
Errno::EADDRINUSE: Address already in use - bind(2)
in the output window?Either because there is another process running which is using ports 8989/8990 or the last debugger process is still alive (killall ruby
will solve that).
RubyDebugger is released under the MIT License.