AppCode 2016.3 Help

Debugging

AppCode comes bundled with an LLDB debugger.

General debugging steps

  1. Configure the debugger options.
  2. To debug CoffeeScript, TypeScript, and Dart code, you need source maps generated in addition to the JavaScript code.

    Source maps set the correspondence between lines in your original code and in the generated JavaScript code, otherwise your breakpoints will not be recognised and processed correctly.

    JavaScript and source maps are generated by transpiling the original code either manually using the File Watcher of the type CoffeeScript, or by the built-in compiler (for TypeScript), or through integration with the Pub Serve tool (for Dart). After that, you can debug the output JavaScript code. See Transpiling CoffeeScript to JavaScript, Transpiling TypeScript to JavaScript, and Using Integration with the Pub Tool for details.

  3. Define a run/debug configuration for the application to be debugged.
  4. Create breakpoints in the source code.
  5. Launch a debugging session.
  6. Pause or resume the debugging session as required.
  7. 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/2016.3/debug.png icon that marks the Debug tool window toggles to /help/img/idea/2016.3/debug_active.png to indicate that the debug process is active.

See Also

Last modified: 28 March 2017