RubyMine 2017.2 Help


General debugging steps

  1. To debug CoffeeScript, TypeScript, and Dart code, you need to generate a source map for it. This will set the correspondence between lines in your original code and in the generated JavaScript code. If no source map is generated, your breakpoints will not be recognized and processed correctly.
  2. Define a run/debug configuration for the application to be debugged.
  3. Create breakpoints in the source code.
  4. Launch a debugging session.
  5. Pause or resume the debugging session as required.
  6. During the debugger session, step through the breakpoints, evaluate expressions, change values on-the-fly, examine suspended program, explore frames, and set watches.

After you've started a debug session, the /help/img/idea/2017.2/debug.png icon that marks the Debug tool window toggles to /help/img/idea/2017.2/debug_active.png to indicate that the debug process is active.

Important note

Debugging in RubyMine is possible in two ways:

  • using the built-in debugger, which you will be prompted to install the first time you begin debugging your application, depending on the Ruby version (e.g.: ruby-debug-ide, debase, ruby-debug-base19). Compatible gems of the built-in debugger will be installed into Ruby SDK.
  • using external debugger gems, like debugger(for Ruby 1.9) or byebug(for Ruby 2.x). Both of them require gem debugger-xml installed into SDK. This gem provides graphical interface for external debuggers.
Last modified: 26 October 2017

See Also