« Mandatory identification for all internet forums? | Main | Expanding Horizons »

Komodo Remote Debugging, Part 2

Luckily, I now have half of a solution to the Komodo Remote Debugging issue I previously wrote about, thanks to Peter.

I still don't have a solution to the PerlEx debugging issue. No matter how hard I try, there's no way I can get it to communicate with Komodo. I'm not too worried about it, though. It's not often you need to debug a perl application while in production, and I can deal with it later.

Peter found the same issue that I did. ActiveState's documentation states that you must change the application mapping in IIS to reflect 'perl.exe -d "%s" %s' to get perl to go into debug mode. This doesn't work, for a variety of reasons. Turns out, if you change the shebang in your cgi (#!/usr/bin/perl and the like) to add -d, but leave it out of the app mapping, debug mode starts up properly.

Sure enough, I tried it out on my IIS machine in a virtual directory, went to the script, and Komodo lit up just fine on my Mac.

Thanks, Peter.

TrackBack

TrackBack URL for this entry:
http://www.abstractwankery.com/cgi-bin/mt4/mt-tb.cgi/12

Listed below are links to weblogs that reference Komodo Remote Debugging, Part 2:

» Komodo Remote Debugging from abstractwankery.com
I'm on a Komodo kick here, sorry about that. I'm having some hell of a time trying to figure out remote debugging within Komodo. So I'm using Komodo Personal 3.5 on Mac OS X, test environment is a Windows XP... [Read More]

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)