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 SP2 machine running IIS, no firewall, no port blocking, no antivirus, no antispyware. Komodo's running on a Mac OS X 10.4.5 machine.

I have:

• Installed the Windows Remote Debug for Komodo package (to c:\Perl \KomodoDebug)
• Set Komodo to listen to port 9000
• Set PERL5LIB to C:\Perl\KomodoDebug
• Set PERLDB_OPTS to RemotePort=[my mac's ip]:9000
• From the command line, started perl -d , and Komodo successfully did the remote debugging thing.

So, now I want it to work in IIS. Specifically, I want to know why this application dies in certain modules under PerlEx 3 with the ActiveState Perl 5.8.7 (815) package.

First, I tried changing the app mapping in IIS to 'c:\perl\bin\perl.exe -d "% s" %s', and it prompts for me to download the application. I manually edit the MIME types in IIS to always output text/html, and it just spins and spins and spins in the browser.

Okay, fine, I'll skip the perl CGI and go to PerlEx.

I create a key in HKLM/SOFTWARE/ActiveState/PerlEx/3.0/Classes called 'nx-d'. Inside are three string values: (LF being the ALT-1-0 trick)
CommandLineOptions = -d
Environment = PERL5LIB=C:\Perl\KomodoDebug[LF] PERLDB_OPTS=RemotePort=[my mac's IP]:9000
ScriptLocation=[full path to script, starting with c:, using backticks. seems to work.]

When running the CGI, it spins and spins and spins and never starts anything within Komodo on the OS X machine. I've noticed, once in a while, Windows shows an application unexpectedly quit issue regarding a COM loader. This is probably related.

I don't friggin get it. I was hoping writing it down would make some light bulb go off in my head.

No such luck.

Update: Debugging is now working using the standard perl executable!