Aptana Studio 3 not able to run ruby debugger after update

Aaron Patterson's Avatar

Aaron Patterson

25 Jul, 2011 02:17 PM

Windows 7
Aptana Studio 3 version
Ruby 1.9.2

I updated Aptana Studio 3 to last week. Since the update, I have not been able to do any debugging.

I was part of this discussion, "https://aptanastudio.tenderapp.com/discussions/problems/2896-issues...", and the addition of the RUBYLIB environment variable to my debug configuration had solved that problem. Now I keep receiving this error whenever I try to debug my ruby application: "C:\Ruby\Ruby192\bin\rubyw.EXE: No such file or directory -- Studio (LoadError)"

I checked the error log and it says:
!ENTRY org.eclipse.core.jobs 4 2 2011-07-25 09:41:57.161 !MESSAGE An internal error occurred during: "Launching CFE Documentation". !STACK 0 com.aptana.ruby.internal.debug.core.DebuggerNotFoundException: Could not connect to debugger on port 53791

at com.aptana.ruby.internal.debug.core.commands.AbstractDebuggerConnection.getSocket(AbstractDebuggerConnection.java:93)
at com.aptana.ruby.internal.debug.core.commands.AbstractDebuggerConnection.createCommandConnection(AbstractDebuggerConnection.java:75)
at com.aptana.ruby.internal.debug.core.commands.RubyDebugConnection.connect(RubyDebugConnection.java:22)
at com.aptana.ruby.internal.debug.core.RubyDebuggerProxy.start(RubyDebuggerProxy.java:79)
at com.aptana.ruby.internal.debug.core.launching.RubyDebuggerLaunchDelegate.launch(RubyDebuggerLaunchDelegate.java:113)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:924)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1128)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

I've double-checked the windows directory to make sure rubyw.EXE was actually at that location, and it is. The only difference I could find was the capitalization of "exe". It is lowercase in the actual windows directory, but that has no bearing on the error. (I checked.)

I am still able to run the normal server.

  1. Support Staff 1 Posted by Chris Williams on 25 Jul, 2011 03:25 PM

    Chris Williams's Avatar

    I've opened a bug for this issue here: http://jira.appcelerator.org/browse/APSTUD-3075

  2. Chris Williams closed this discussion on 25 Jul, 2011 03:25 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac

Recent Discussions

24 Mar, 2015 02:21 AM
16 Mar, 2015 07:17 PM
12 Mar, 2015 03:30 PM
12 Mar, 2015 10:33 AM
11 Mar, 2015 03:25 AM

Recent Articles