To others out there trying to get it to work: just copy & paste the debugger initialization into David Esposito’s wrapper. `rake restart DEBUG=true` and you’re good to go! The debugger can be connected well in advance of the breakpoints if you have one further into your application.

I’m not sure when the spawning code was added/changed in Passenger, but the code above will not work with Passenger 2.2.4. Putting the code to launch the debugger in environment.rb (or development.rb) means that it launches within the ApplicationSpawner process and the Rails requests are handled in separate worker processes so your breakpoints will never get hit.

Section 11.3 of the Passenger guide gives a technique for ensuring that you can hook the spawning of a new request handler. You’ll want to put the code outlined above in the ‘if forked’ block. You will need a little extra code to preserve the state of debug.txt (whether it existed when Apache was tickled) and if your Passenger is configured to allow multiple workers (the default), you’ll have trouble identifying which listener is debugging which process

http://www.modrails.com/documentation/Users%20guide.html#spawning_methods_explained

Lastly, you can debug your Rails app from NetBeans by using the ‘ruby-debug-ide’ gem instead of the ‘ruby-debug’ gem.

Here’s my code in development.rb (it launches the debugger every time without regard to debug.txt)

if defined?(PhusionPassenger)
PhusionPassenger.on_event(:starting_worker_process) do |forked|
if forked
require ‘ruby-debug-ide’
Debugger.cli_debug=true
Debugger.start_server(nil,7000)
end
end
end

[...] für Rails-3-EntwicklungWie man den Phusion Passenger für die Entwicklung benutzt wurde schon an einigen Stellen beschrieben. In Verbindung mit Rails 3 gibt es eine kleine Falle. Folgt man diesen [...]

[...] http://duckpunching.com/passenger-mod_ra… http://duckpunching.com/passenger-mod_rails-for-development-now-with-debugger [...]

[...] wait, there is hope: here is a great post on how to debug remotely using ruby-debug. The other option that i tried was using [...]

[...] 下面比较一下二者： 1. 同时对多个本地app进行开发时，passenger比webrick好。因为不需要对于每个app都开一个webrick server，而且对于每个server还需要指定不同的port。 2. 在查看request的信息方面，passenger和webrick差不多。webrick是直接在terminal中显示每个request的信息;而在使用passenger时，则可以通过动态显示development.log的方式进行查看。 3. 在debug方面，webrick会比passenger方便些。在使用webrick时，只需要使用u option来启动server，那么app就会在运行时中断在程序中写有debugger语句的地方。可是，在使用passenger时，debug可能会比较麻烦。目前看到的有两种方式，一种是通过使用remote debug的方式，具体可以参考Passenger (mod_rails) for development. Now with debugger! 。另一种是使用rack-debug，它是一个ruby-debug的interface，其使用方式和webrick没有多大区别，但是唯一一点令我难受的时，对于每个rails app，都需要添加一个middleware来实现rack-debug的功能，但是由于可以通过version control在真正的app里过滤掉这些文件，其实并没有多大影响。 [...]

[...] 2:55 pm on October 19, 2009 Reply Tags: debugging, rails (69), tutorials (5) http://duckpunching.com/passenger-mod_rails-for-development-now-with-debugger – Passenger (mod_rails) for development. Now with debugger! [...]