AppCode 2016.1 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 manually using the File Watcher of the corresponding type (CoffeeScript, TypeScript, or Dart). After that, you can debug the output JavaScript code.

    For details, see Using File Watchers, Transpiling CoffeeScript to JavaScript, and Transpiling TypeScript to JavaScript.

  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 debug icon that marks the Debug tool window toggles to debug_active to indicate that the debug process is active.

If you want to see a list of all currently running applications, select Run | Show Running List from the main menu. A popup listing all active applications will be displayed in the top-right corner of the editor.

See Also

Last modified: 20 July 2016