ActiveState Community

hi, I am a beginner on both perl and linux. I have created a Perl program on my windows Komodo 4.1 IDE and send by FTP to my linux REHL4 development, no firewall. I have also downloaded activePerl-5.8.8.820 and KomodoPerlremoteDebugging4.1.1-279677-linux-x86 in my linux server. ActivePerl is rpm packet so it was no problem to install, by contrast to remoteDebugginng. After unpacking tar file i have got perl5db.pl, license.txt files and two folders.

Folks:

Sorry to clutter the forum with &^%$# xdebug-install-related questions, but it's such a crucial piece of the komodo apparatus and I'm just not finding docs that support tractable DIY troubleshooting. Specifically:

1. Where is authoritative documentation on the zend_extension option or variable and its use in php.ini?

Folks: Little hair remaining after this ordeal. Simply trying to get any kind of php debugging working in komodo 4.1 on linux. Local CLI debugging would be a start, but also of course want to debug apache-served scripts.

1. Komodo didn't set up xdebug automatically.

2. The Debug config wizard put php.ini and xdebug.so in the right place (and commands in php.ini), but fails saying:
"WARNING: koPHPConfigurator: PHP is configured, but was unable to load the debugger extension at [/opt/Komodo-IDE-4.1/lib/support/php/debugging/5.2/xdebug.so]."

Folks:
I've installed Komodo IDE 4.1 on my Centos 4 (RHEL 4) box. Had to use libcpp5, due to libcpp6 wanting some additional dependencies not in RHEL4.

I installed it while logged in as root, and it appears to start up fine, and proceeds to a tutorial OK.

But now I want to use it as a regular user. So I login as regular user and start up komodo, but I immediately get a message "Your installed license is not compatible with this version of Komodo", and it offers to upgrade/renew only.

It would appear that the current Perl debugger stub has no understanding of fork(). In my test case (see below), the code continues to execute in both the child and parent processes, and the debugger UI is being updated by both. This is particularly annoying when you hit a breakpoint in one process and then the other process updates the debugger UI state because it is still running.

I have disabled the alarm routine in the perl5db.pl due to a problem I am having with a multithreaded application. However, this does not disable the "break" button in the Komodo GUI. I would have assumed that if I told the debugger that break was disabled in the DGBP feature negotiation that the button would be disabled.

I set the following:

$supportedCommands{break} = 0;
$supportedFeatures{supports_async} = [0, 0, 0];
$settings{supports_async} = [0];

And here is the DGBP feature negotiation confirming break is not supported:

feature_get -n break -i 11

Hi there,

I've a system with RedHat 7.3 (I need this because of it's glibc version) and I'm trying to install ActivePerl and PDK on it.

I've installed ActivePerl 5.8.8 without any problem. When running the "install.sh" of PDK 7.0 I receive this message:

Error: Can't locate libperl.so

I've tryed MANY things (the activeperl dir is in the path already) but without success. PDK 6.0 works fine on ir.

Any clue about this?

Has anyone figured out how to get STDOUT and STDERR printing to separate tabs in Komodo, when using the debugger? I'm writing Perl, and generally the 'warn' msgs and the 'print' msgs are way out of synch in the output. (I guess another question would be, what's the best way to synchronize the STDOUT and STDERR output?)

TIA

Hi Chaps,

Great product, thank you.

Any chance for extending SCC by adding support for Mercurial?

Thanks,

D.