ActiveState Community

I've just installed the latest build of IDE5.2 and it still crashes as soon as I boot it up. I have to reboot my computer (AMD64) before I can try it again because once it's crashed, it won't restart,
Actually, it is still showing as running in the system monitor, but the program is invisible. If I kill the process I can restart Komodo, but as soon as I try to open a file it crashes again.

Any ideas??

Under Linux I experience Komodo IDE as quite slow.

For almost all UI actions (opening a find dialog, clicking a file in the project view, stepping in debugger, ...etc) there is approximately a 1-2 second delay before anything happens. This is before the UI reacts at all, not including any processing or remote response.

I have some colleagues which use Komodo on a Mac, this UI delay is not so apparent there.

I spend many days in debuggers so responsiveness and overall application feeling is important to me.

While breakpoints in normal .pl files are handled alright, if I include a .pm file via use, none of the breakpoints I set in the .pm file are stopped at. This is very frustrating and hope I am doing something wrong which can be fixed.

I get these warnings when I start Komodo 5.1/5.2 on Ubuntu 9.04:

Gtk-Message: Failed to load module "canberra-gtk-module": /usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: wrong ELF class: ELFCLASS64
Gtk-Message: Failed to load module "canberra-gtk-module": /usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: wrong ELF class: ELFCLASS64
/usr/lib/gio/modules/libgioremote-volume-monitor.so: wrong ELF class: ELFCLASS64
Failed to load module: /usr/lib/gio/modules/libgioremote-volume-monitor.so
/usr/lib/gio/modules/libgiogconf.so: wrong ELF class: ELFCLASS64

I'm getting started on Ubuntu packaging for Open Komodo. One item that's going to be an issue right away is Mozilla. The way the build system downloads Mozilla sources and applies patches is neat, but Debian/Ubuntu packages have to have all sources available at build time. I noticed a tarball option for mozilla/build.py which could probably work. Any hints on where to get this tarball? I noticed Mozilla provides tarballs of source releases but I don't know which might apply here. Any guidance is appreciated.

Hi,

I am solving a problem concerning a race condition (probability cca 1:1000) in a distributed system (python code) and would require as much information as I can get from problematic running process (logging is insufficient).

AFAIK there is no way to attach to already running python process with any debugger (except low-level GDB). In a similar manner, it is not (easily) possible to generate equivalent of "python coredump", os.abort() dumps core, but needs to be inspected with GDB (very tedious compared to python-level debugger like Komodo).

"Coredump" via CryoPID

I've been using Komodo 5.1 on Ubuntu for some months now, and it works pretty well. I've been using Firebug for JavaScript debugging, but see there's a JavaScript debugging extension for Komodo; I installed it to Firefox using the "Install/Update 'Komodo JavaScript Debugger' Firefox Extension" button under Language/JavaScript.

Though this is neither a snippet nor a macro, I think it is a trick worth sharing.

It is for ubuntu/linux, but I'm sure, it can be adopted to other OS as well.

The story

All my projects are organized like this

|_projects
...|_example.com
......|_example.kpf
......|_template#1
.........|_root
............|index.html
............|_css
............|_images
...
|_templates
...|_template#1
......|_root
.........|index.html
.........|_css
.........|_images
...
|_template#2
...
|_template#n

Hi,

I need some help getting the debugger going for Komodo 5 on Ubuntu Jaunty and a 64-bit box.

Things are mostly working right now:

I have xdebug installed
I have Komodo listening on port 9000
A simple test script that calls xdebug_break manages to connect to Komodo
Komodo shows the source file and the correct line number

The problem is that when I try to single step, the script runs to completion and never comes back. This also happens for the actual script I'm trying to debug.

Here is the script: