The Komodo installer will prompt for an installation directory; you can choose any directory you have permissions to install to. The default location varies by platform, and the name of the directory corresponds to the version of Komodo you are running ("IDE" or "Edit" on Windows, "IDE" or "Edit" plus the version number on OS X and Linux):
C:\Program Files\ActiveState Komodo [IDE|Edit]\
Note: Older versions of Komodo on Windows installed in a directory which included the version number (e.g. "ActiveState Komodo IDE 4.2"), which allowed for side-by-side installations of different versions of Komodo. If you wish to do this, manually specify an install directory with a version number.
Komodo stores preferences, userscripts, templates, keybinding schemes and other settings in a user-specific directory called the user data directory. The name and location of this directory varies depending on the operating system and Komodo version:
Mac OS X
The location of this directory can be overridden using the
KOMODO_USERDATADIR environment variable.
The user data directory contains
pystdout.log, which can be useful for troubleshooting problems with Komodo.
If Komodo doesn't start, there could be one of several issues.
Do you have Norton Anti-Virus (NAV) installed, or more specifically, the File System Realtime Protection feature enabled?
The problematic relationship between Komodo and Norton Anti-Virus' File System Realtime Protection feature is a known issue, which we are working to remedy. In the meantime, you can disable
NAV Corp 7.5 FSRP before running Komodo, and then re-enable it after Komodo starts.
If none of these seem to apply to you, please follow the instructions in this FAQ entry to log a bug in Komodo's bug database.
One or more panes may be hidden.
To view the Left Pane, click the Show/Hide Left Pane button on the toolbar, use the options on the View menu, or use the associated key binding.
The Bottom Pane appears below the Editor Pane during debugging. If you can't see your Bottom Pane, it may be hidden.
To view the Bottom Pane, click the Show/Hide Bottom Pane button on the toolbar, use the options on the View menu, or use the associated key binding.
For more information, see Debugging Programs
I like to see the Left and Right Panes and the Bottom Pane, but right now I want to maximize my Editor Pane to get some coding done. How can I maximize my Editor Pane?
To maximize your Editor Pane, hide the other panes in the Komodo workspace:
When Komodo is debugging, the title of the Komodo workspace includes an indication of the state of the debugger. If the debugger is running, the title looks similar to [pathname\filename] - ActiveState Komodo - Debugger is running. If the debugger has hit a breakpoint, the title looks similar to [pathname\filename] - ActiveState Komodo - Debugger is in Break Mode.
You are editing any time you're not formally debugging. When Komodo is editing, the title of the Komodo workspace is [pathname\filename] - ActiveState Komodo.
If you want to send add command-line arguments to your program for debugging, you can add these using the Debugger Launch Options dialog:
As Komodo is running it updates a few log files with debugging and error information. If Komodo crashes, you can help us best determine the issue by sending us those log files, along with information on how you came across the crash. On some operating systems the system creates a crash log as well, which you should also send to us. The log files may include:
Please use the following steps to send us your crash information:
Step 1: Ensure the logs are for the time Komodo crashed
Komodo's log files are only for the last time Komodo was run. If you have restarted Komodo since the time it crashed on you, you must reproduce the crash so that the log files are relevant.
Note: If Komodo is hung (i.e. won't shutdown), you may need to manually stop the
Step 2: Locating the error log files
On Mac OS X, an additional
komodo-bin.crash.log is created by the system in
Step 3: Verifying and sending the files to ActiveState
To send the error log files to ActiveState:
Because Komodo is built on the Mozilla framework, it is necessary for us to include the Mozilla build that exactly matches the development version of Komodo. For that reason, even if you have Mozilla on your system, Komodo installs the Mozilla version that it requires.
Another sizable component of Komodo is language support. Komodo is so tightly integrated with Perl, Python, Ruby and PHP that it is necessary to include components of those languages, at specific version levels, for debugger and editor support.
When ActiveState develops a Komodo release, the work is based upon a specific version of Mozilla. During the development process, we upgrade the level of Mozilla used by Komodo, but this process requires considerable testing to ensure that no functionality is lost. Additionally, we add some custom components to the Mozilla tree that are used by Komodo. For these reasons, we recommend that you do not replace the Mozilla version included with Komodo with a later Mozilla version.
If you receive an error message when attempting to debug a PHP program or if the debugging process does not proceed as expected, verify that you have installed PHP and the Xdebug extension as per the instructions in the Debugging PHP documentation, then check the following:
Confirm PHP Configuration
php -m. "xdebug" should be listed under Zend Modules (and not under PHP Modules). If this is not the case, your configuration is incorrect. See "Common PHP Configuration Problems" below.
<? asdf echo test; ?>
Komodo should display a red squiggly line under `echo test;`. If it does not, it indicates that Komodo is not able to communicate with the PHP interpreter.
If any of the steps above were unsuccessful, proceed to the next section.
Common PHP Configuration Problems
Verify Xdebug library specification: The location of xdebug.dll (Windows) or xdebug.so (Linux) must be defined the php.ini file, for example:
Windows-Specific Configuration Issues Version Error Messages
If you receive a dialog with the following text:
Warning xdebug: Unable to initialize module Module compiled with debug=0, thread-safety=1 module API=20001222 PHP compiled with debug=0, thread-safety=1 module API=20001222 These options need to match
... download an updated version of
xdebug.dll (Windows) or
xdebug.so (Linux) from the Xdebug.org site.
Though it is possible to emulate sessions in local debugging mode, this requires pre-knowledge of session keys, and how those session keys are communicated to PHP.
It is easier to debug sessions using remote debugging. Run the script under a web server and start the debugging session from a web browser. Komodo intercepts the session and debugs it. All session data is available and modifiable through the Variable tabs.
When debugging Python programs that use Psyco, the breakpoints will be ignored. This is due to the optimizations/changes made by the psyco compiler.
You can work around this problem with the following code which disables Psyco while debugging:
import logging if not logging.Logger.manager.loggerDict.has_key('dbgp'): import psyco psyco.full()
Virtual Hosting is an Apache feature for maintaining multiple servers on the same machine, differentiating them by their apparent hostname. For example, a single machine could contain two servers, "www.yourdomain.com" and "debug.yourdomain.com".
If you have configured your Apache installation to use Virtual Hosting (see httpd.apache.org/docs/1.3/vhosts/), you can add directives to your VirtualHost sections to specify how Komodo's PHP debugger extension operates for those hosts. Use the "phpadminvalue" to set specific debugger settings for that virtual host. Here is an example:
NameVirtualHost * <VirtualHost *> php_admin_value xdebug.enabled 0 DocumentRoot "/Apache/htdocs/" ErrorLog logs/www.error.log Servername www.yourdomain.com </VirtualHost> <VirtualHost *> php_admin_value xdebug.enabled 1 DocumentRoot "/Apache/htdocs/" ErrorLog logs/debug.error.log Servername debug.yourdomain.com </VirtualHost>
This will enable debugging under debug.yourdomain.com, but not under www.yourdomain.com. You can additionally configure the Virtual Host to use a specific machine for remote debugging:
<VirtualHost *> php_admin_value xdebug.enabled 1 php_admin_value xdebug.remote_host komodo.yourdomain.com DocumentRoot "/Apache/htdocs/" ErrorLog logs/debug.error.log Servername debug.yourdomain.com </VirtualHost>
For more information on configuring Virtual Hosting under Apache, see the Apache documentation at httpd.apache.org/docs/.
On Linux, you cannot relocate an existing Komodo installation to a new directory. You must uninstall Komodo from the existing location and reinstall it in the new location. See Uninstalling Komodo on Linux for instructions.
To prevent the debugger dialog from appearing each time you start the debugger, hold down the 'Ctrl' key when you start the debugger. For example, on Windows and Linux, press 'Ctrl'+'F5' rather than 'F5' to start debugging. Click Help|List Key Bindings to find the equivalent key binding for the Emacs and OS X default key binding schemes.
The CGI security alert only occurs when you compile PHP with --enable-cgi-force-redirect. That compilation directive forces PHP to check if it is being run as a CGI by looking at environment variables commonly available only under a CGI environment. If they exist, it looks for another environment variable that is reliably available ONLY under Apache, REDIRECTSTATUS (or HTTPREDIRECT_STATUS under Netscape/iPlanet). If that environment variable does not exist, the security alert is generated.
To run your compilation of PHP under Komodo with CGI emulation, you have to add a CGI environment variable called REDIRECT_STATUS with any value.
In order for Komodo to detect the presence of a language installed on your system, the location of the language interpreter must be specified in your system's
PATH environment variable. If the Check Configuration dialog states that a language is "Not Functional", or if the Komodo Preferences say that the language interpreter is not found on your system, check that the interpreter is specified in your
Komodo launches a process as part of the background syntax checking that can cause a full screen command prompt to momentarily appear on some Windows systems. You can make the process invisible by editing the properties for the command prompt window. On the Windows Start menu, right-click the Command Prompt item, and select Properties. Select the Options tab, and change the Display options to Window.
Komodo can be used to check out, add, remove, compare, submit and revert files in a CVS repository. CVS offers additional commands such as import, checkout, history, annotate, rdiff and watch which can be put into Run Commands and saved to a project or the Toolbox. For example, the following
cvs import command prompts for the User, Host, Module, Project and Version to import:
cvs -d :ext:%(ask:User)@%(ask:Host):%(ask:Path) import %(ask:Module:) %(ask:Project:) %(ask:Version:)
%(ask:...) interpolation shortcut could be populated with defaults or replaced with static values:
cvs -d :ext:%(ask:User:jdoe)@myhost:/var/cvsroot import %(ask:Module:) %(ask:Project:MyProject)
CVS requires a real terminal for adding change descriptions. Be sure to set Run in: New Console in the command's properties.
Linux users trying to debug a Ruby application on AMD 64bit systems may see the following error:
The Komodo ruby debugger couldn't load the ruby-debug-base component.
This library ships with Komodo, but also can be installed by running `gem install ruby-debug-base'
Komodo ships with a 32-bit version of ruby-debug-base, which will not work with 64-bit versions of Ruby. To fix this:
ruby-debuglibraries by removing the
sudo gem install ruby-debug-base-0.10.x.gem
Komodo will automatically find and use the new version of the debugging library.
© 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.