This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 125340 - Can't debug after switching from Rails 1.1.6 to Rails 1.2.6
Summary: Can't debug after switching from Rails 1.1.6 to Rails 1.2.6
Status: RESOLVED WORKSFORME
Alias: None
Product: ruby
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Martin Krauskopf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-16 04:58 UTC by dmoulton
Modified: 2008-03-17 08:53 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
logfile output (6.40 KB, text/plain)
2008-01-16 14:38 UTC, dmoulton
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dmoulton 2008-01-16 04:58:16 UTC
I recently switched from using rails 1.1.6 to rails 1.2.6. I have discovered that I cannot debug my project. If I switch
the project back to 1.1.6 (in environment.rb), debugging is fine. When using 1.2.6, I cannot set breakpoints.

I am using Ubuntu 7.10, and NB 6.0 release 200711261600. This machine dual boots, so I installed NB on windows, and
loaded up the same project. It debugs just fine using rails 1.2.6.

I am using a fresh install of NB 6 on Linux, and still have the problem. If I create a new rails app that is 1.2.6
based, it debugs fine.

Here is the output from the debugger log:

FINEST [org.netbeans.modules.ruby.debugger.Util]: Performing "kill"
FINEST [org.netbeans.modules.ruby.debugger.Util]: Finishing session: localhost:39641
FINE [org.rubyforge.debugcommons.Util]: Sending command debugger: exit
INFO [org.rubyforge.debugcommons.Util]: finished
FINE [org.rubyforge.debugcommons.Util]: Got <message>, text == finished
FINE [org.rubyforge.debugcommons.Util]: ReadersSupport readloop [class org.rubyforge.debugcommons.ReadersSupport command
loop] successfully finished.
FINE [org.rubyforge.debugcommons.Util]: Trying to finish the same proxy more than once:
org.rubyforge.debugcommons.RubyDebuggerProxy@1133663
FINEST [org.rubyforge.debugcommons.Util]: Socket reader loop finished.
FINEST [org.netbeans.api.ruby.platform.RubyInstallation]: Looking for 'rdebug-ide' gem executable; used intepreter:
'/usr/bin/ruby1.8'
FINEST [org.netbeans.modules.ruby.debugger.Util]: Using timeout: 10s
FINEST [org.netbeans.api.ruby.platform.RubyInstallation]: Looking for 'rdebug-ide' gem executable; used intepreter:
'/usr/bin/ruby1.8'
FINE [org.rubyforge.debugcommons.Util]: Running [basedir: /home/dmoulton/projects/rails125]: "/usr/bin/ruby1.8 -r
/tmp/io-synchronizer8646.rb /usr/bin/rdebug-ide -p 33939 -d -- script/server --port 3000"
FINEST [org.rubyforge.debugcommons.Util]: Cannot connect to localhost:33939. Trying again...(19)
FINE [org.rubyforge.debugcommons.Util]: Sending command debugger: b
/home/dmoulton/projects/rails125/app/controllers/support_controller.rb:228
FINE [org.rubyforge.debugcommons.Util]: Starting ReadersSupport readloop: class
org.rubyforge.debugcommons.ReadersSupport command loop
FINE [org.rubyforge.debugcommons.Util]: Sending command debugger: start
FINEST [org.rubyforge.debugcommons.Util]: Waiting for breakpoints.
Comment 1 Martin Krauskopf 2008-01-16 08:21:14 UTC
Hi. The "Waiting for breakpoints" was the last debugger message in the log, right?
The attached log seems OK. Few things might help:

- attaching the second log, the content output window, as described in the wiki. Note you might attach large contents as
  attachments into Issuezilla.
- switching to NB 6.0 final or dev build and see if that helps. It might be some older bug.

Also to be sure that code goes through the place where the breakpoint was set (by e.g. putting there simple 'puts
"something"). But likely this is not the case.

Comment 2 dmoulton 2008-01-16 14:38:23 UTC
Created attachment 55148 [details]
logfile output
Comment 3 dmoulton 2008-01-16 14:41:25 UTC
I am using NB 6 final. I know the breakpoint is in the right place, because if I leave everything as is, and switch
environment.rb back to 1.1.6, it then stops there.

Thanks for the troubleshooting help, I'll keep trying. I'll try checking out the project again from svn and a few other
things today.
Comment 4 Martin Krauskopf 2008-01-16 17:27:03 UTC
Did you try to add breakpoint to some other files? Actually it would help to put it in "a lot of" places. Like into
config/environment.rb. Just to see whether the debugger fails to stop only in ERB templates or in all files.
Comment 5 dmoulton 2008-01-16 18:24:21 UTC
It does stop fine on breakpoints in the config directory, ie environment.rb and development.rb. It also stops in
script/server, etc. This is all as the server is starting up, obviously.

It will not stop on any controller or view file after the server is started. I'm trying to get it to stop in
application.rb currently.
Comment 6 Martin Krauskopf 2008-01-16 18:35:58 UTC
Quite strange. I suppose it is not possible to get the application (since with new application (and all others?) it
works). Just with that one. The best would be to hunt it into some simple scenario.

Also would worth it to test the application with the CLI debugger 'rdebug'. This would show whether the problem is in
NetBeans or in some lower debugger layer (we are using the same as CLI debuger ruby-debug gem).

Also I've lost the track if you tried it with dev build - but it might be little unstable.

There are more ways to go. I'm just not able to reproduce in any way my self. Anyway I'm going to get back to the
debugger works in the next days, so if nothing helps we can put some logging into dev build to catch it.
Comment 7 dmoulton 2008-01-17 04:07:22 UTC
Thanks alot for all the help. I haven't tried a dev build yet. I'll do that. I'll let you know if I can get it figured out.

I'll let you change the status of this issue to whatever you feel like.
Comment 8 Martin Krauskopf 2008-02-27 15:08:00 UTC
Hi, did you try with the 6.1 dev builds?

  http://wiki.netbeans.org/RubyInstallation#section-RubyInstallation-DownloadLocations
  (-> Continuous builds)

Let me know if you are still encountering the problem.
Comment 9 Martin Krauskopf 2008-03-17 08:53:58 UTC
Please reopen the issue if you are still able to reproduce with latest dev build. See my previous comments how to
provide more info. Thanks.