ActiveState Community Site - komodo - Comments

On Komodo IDE 4.4 on Mac

simon29 — Mon, 01 Dec 2008 19:30:00 -0800

On Komodo IDE 4.4 on Mac OSX, the komodo command opens a new instance of the application rather than opening the file as a new tab in the already running instance. Bit of a shame, that would've been very handy. I often used Textmate from the command line.

Yeah, from a stock OS X

jeffg — Mon, 27 Oct 2008 13:17:39 -0700

Yeah, from a stock OS X installation you will of course need to create the bin directory in your user directory. Or you can really use *any* directory to create the symlink in as lng as that directory is on your PATH.

--
JeffG
http://www.openkomodo.com/blogs/jeffg

Path not found on Mac OSX

Rimian — Fri, 24 Oct 2008 18:41:02 -0700

Hello,

Oh no! I have no /Users/username/bin directory.

Extend your trial

mrjcleaver — Wed, 30 Jul 2008 11:23:00 -0700

I was told to login to activestate and extend my trial - this would reset the hostname the trial is tied to.

Also, my ~/Library/Application\ Support/ActiveState/ was owned by root.

Resetting ownership to be owned by my user enabled the trial licence to work.

Martin.

32 bit libs and Hardy 8.04 64 bit version

pannerrammer — Wed, 25 Jun 2008 03:36:09 -0700

The ia32-libs-gtk item shouldn't be there. This works

sudo apt-get install binfmt-support ia32-libs libc6-i386

Comment out doc_root line in php.ini

troyt — Thu, 12 Jun 2008 13:48:55 -0700

It looks like doc_root setting in the php.ini bundled with Web Developer Suite 2.0 causes problems for the remote debugger. Comment out that line in c:\www\php5\debug\php.ini and it should work.

Thanks for bringing this to our attention! We'll create a bug for Komodo to handle this better and mention it in the release notes, but it's unlikely to be fixed in time for the 4.4 release.

Re: try latest Komodo (4.3.2)

osmosis — Tue, 10 Jun 2008 17:51:29 -0700

Thanks for the help Todd.

I'm using:

Komodo IDE, version 4.4.0-beta1, build 19400, platform win32-x86.
Built on Fri May 30 02:25:59 2008.

Web Developer Suite 2.0 which includes Apache 2.2 and PHP 5.2.5
http://sourceforge.net/projects/webdeveloper/

Preferences, PHP Language:

Interpreter: c:\www\php5\php.exe
php.ini: c:\www\php5\debug

I also tested with c:\www\php5\php-cgi.exe and received the same results.

the debug\php.ini was created during installation of Komodo. It's the default php.ini with the following prepended from Komodo:

; xdebug config added by Komodo
zend_extension_ts=C:\www\php5\ext\php_xdebug.dll
xdebug.remote_enable=1
xdebug.remote_handler=dbgp
xdebug.remote_mode=req
xdebug.remote_port=9000
cgi.force_redirect = 0

I verified that those parameters are commented out everywhere else in the php.ini file.

Choosing Debug -> Go/Continue:

I choose "Use the CGI interpreter"

I check "Simulate CGI Environment"

and I add the post values according to the debugging PHP tutorial / demo.

It works if I choose "Use the CLI interpreter", but then it doesn't allow me to specify the post variables.

The only thing I can think to add at this point (in case it helps) is a copy of the php.ini along with lists of extensions enabled in php.

Re: try latest Komodo (4.3.2)

ToddW — Tue, 10 Jun 2008 10:57:00 -0700

Can you try using Komodo 4.3.2 or the Komodo 4.4 beta:
http://downloads.activestate.com/Komodo/releases/

If that does not fix the problem, we'll need some additional details like:
* where did you download PHP from
* how are performing the CGI debugging (through Komodo's Debug - F5 command)
* which interpreter is set in your PHP language preferences

Thanks,
Todd

any other ideas?

osmosis — Mon, 09 Jun 2008 21:54:08 -0700

What else could be causing this? I've tried everything above with no luck.

Komodo 4.3 beta
PHP 5.2.5
Windows XP

The trial period ran out before I had a chance to test cgi debugging, so I installed the beta to extend my trial and finish testing things out...

re: ubuntu 8.04 and Komodo remote files

ToddW — Mon, 26 May 2008 10:56:32 -0700

I don't know exactly what changed in Ubuntu, but something in 8.04 is causing 32-bit binary applications to fail on the hostname lookup. See this particular bug for the details and a workaround:
http://bugs.activestate.com/show_bug.cgi?id=76602

I use ubuntu 8.04 64bits

daviscabral — Sun, 25 May 2008 15:27:48 -0700

Edit remote files doesn't work. The follow error appear to me when I select on "Server":
Error: Name or service unknown.

Thanks!

Mainly because I develop on

webPragmatist — Thu, 20 Mar 2008 17:19:32 -0700

Mainly because I develop on many different machines.

The PythonRemoteDebugging package is only for Python

ericp — Thu, 20 Mar 2008 12:14:30 -0700

For Ruby debugging, you only need these files:

[komodo-install-dir]/.../support/dbgp/rubylib
  rdbgp.rb
  rdbgp/
  1.8/ *** Optional -- should be installed with 'gem install ruby-debug-base'

Since you copied the above directory from a Windows machine to a Linux one,
you can't use the binary libraries in the 1.8/ directory -- they were
built for Windows only. Please delete the whole 1.8 directory on your Linux machine.

Then follow the instructions in
[Help|Debugging|Debugging Ruby|Debugging Ruby Remotely]

Generating Ruby projects remotely is way beyond the scope of the tutorial and screencasts I've done. Why not build and develop them locally, and deploy remotely?

Regards,
Eric

Ok.. I am somewhat understanding this :)

webPragmatist — Thu, 20 Mar 2008 04:34:25 -0700

Here's what I have done (I hope this helps others):

Copied the dbgp folder from C:\Program Files\ActiveState Komodo IDE 4\lib\support\dbgp to my Linux home directory ~/Komodo/dbgp/
Downloaded the Komodo-PythonRemoteDebugging package and overwrote ~/Komodo/dbgp/bin and ~/Komodo/dbgp from that package (it also put some files in ~/Komodo/)
Made sure port 9000 was set in Preferences>Debugger>Connection
Ran export RUBYDB_OPTS=remoteport=my.domain.com:9000 in my rails application folder
Ran ruby -I/home/username/komodo/dbgp/rubylib/ -r /home/username/komodo/dbgp/rubylib/rdbgp.rb script/server in my rails application folder
Ran sudo gem install ruby-debug-base as per the below error message suggests

I still get the error:

Error: /home/username/komodo/dbgp/rubylib/1.8/ruby_debug.so: invalid ELF header - /home/username/komodo/dbgp/rubylib/1.8/ruby_debug.so

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'

The documentation isn't really clear what to do with the Komodo-PythonRemoteDebugging package once you download it, so I guessed.

Thanks for your help in advance. Oh, and you didn't say whether this would allow new ruby projects to be generated remotely (as the tutorial demonstrates) using rails .

Remote rails debugging in a nutshell

ericp — Tue, 18 Mar 2008 15:29:09 -0700

This is untested, but here's how I would do it:

Let's assume you're running Komodo on a Windows box called "buckley.acme.com".
Go into Preferences|Debugger|Connection and have it listen on the
specific port 9000, or whatever port is handy. Make sure
the menu item Debug|Listen for Debugging Connections is checked.

On the Linux box, move to the directory containing the file rdbgp.rb,
the main Komodo Ruby debugger file. Run this shell command:

% rdbg=`pwd`

The only reason to do this is because that path is often very
long. We need to type that path twice, in the next command,
so typing four characters going to be easier to read. If you're
going to do this kind of debugging often you might as well give
the variable a more meaningful name and set it in your profile.

Now move to the directory containing your Ruby script, and run
these commands:

% export RUBYDB_OPTS=remoteport=buckley.acme.com:9000
% ruby -I$rdbg -r $rdbg/rdbgp.rb script/server webrick

That should do it.