SketchUp Ruby API Debugger
This is a Ruby debugger framework for SketchUp 2014 and later. The
ruby-debug-ide protocol has been mostly implemented so any Ruby IDE that supports this protocol should work.
|IDE||Stable (126.96.36.199)||Stable (188.8.131.52)|
|NetBeans (with Ruby community plugin)||Good||Untested|
|VS Code (with
Instructions for Windows:
- Download the pre-built dynamic library (SURubyDebugger.dll) from the latest release or build from the sources.
- Copy the DLL into the SketchUp installation directory. As the exact path will depend on the version of SketchUp you have installed, look for a folder similar to the following:
C:\Program Files\SketchUp\SketchUp 2018\ C:\Program Files (x86)\SketchUp\SketchUp 2015\
- Start SketchUp from the command line or the "Run..." dialog:
SketchUp.exe -rdebug "ide port=7000"
Instructions for Mac OS X:
- Install SketchUp 2014 Maintenance 1 Release (version 14.1.1283) or later.
SURubyDebugger.dylibinto the Frameworks directory of the app bundle:
curl -L https://github.com/SketchUp/sketchup-ruby-debugger/releases/download/184.108.40.206/SURubyDebugger.dylib -o /Applications/SketchUp\ 2018/SketchUp.app/Contents/Frameworks/SURubyDebugger.dylib
- Run SketchUp from the command line:
open -a /Applications/SketchUp\ 2018/SketchUp.app --args -rdebug "ide port=7000"
When launching SketchUp with debugging enabled, the following command-line arguments are supported:
-rdebug "ide [port=<number>] [wait]"
port=<number>- Configures the port on which the SketchUp debugger accepts connections from IDEs. This must match the remote debugger port setting configured in the IDE. If not specified, the port defaults to 1234.
wait- Instructs the SketchUp debugger to wait for an initial connection from an IDE before allowing execution to continue. This is necessary to debug scripts that run automatically, for instance when an extension is loaded. When using this option, the SketchUp process will appear to be frozen until an IDE is attached.
While most common debugging functionality has been implemented, there are few TODOs:
- Debugging of multi-threaded execution
- Function breakpoints
- Exception breakpoints
- Are we missing something else? Please report and contribute!
To contribute, please fork the repository, make your changes and submit a pull request.