Debugger commands can be accessed from the Debug menu, by shortcut keys, or from the Debug Toolbar. For a summary of debugger commands, see the Debugger Command List.
To specify which Google Chrome executable Komodo uses for debugging:
See Komodo Debugger Functions for full instructions on using Komodo's debugging functionality.
Note that Komodo needs to launch Chrome with debugging flags for debugging to work, because of this Chrome cannot be running when you start debugging. Once Komodo has started Chrome you can then keep it running. Attempting to debug with a Chrome instance that was already launched outside of Komodo will not work. This is a limitation in Chrome, not Komodo.
To begin debugging on the remote system, run Google Chrome on that remote system with the following command line switch:
Google Chrome recommends port 9222 (and this is what Komodo uses for local debugging).
Then to start debugging with Komodo:
to match your remote system's hostname and Google Chrome remote debugging port.
|**Note**: For Komodo to open an editable copy of the file, a [Mapped URI](debugger#remote_uri_mapping) must be created to link the file on the remote filesystem with the URI Komodo receives from the remote debugger.|
© 2017 ActiveState Software Inc. All rights reserved. ActiveState®,
Komodo®, ActivePerl®, ActivePython®, and ActiveTcl® are registered
trademarks of ActiveState.
All other marks are property of their respective owners.