I'm running passenger enterprise 4.0.0-rc6 locally (development) on my OS X mountain lion with apache under MAMP.
I have a rack app (Sinatra) running through a sub-uri configuration.
Everything works great. Except I can't seem to attach a debugger to the running process successfully.
When I run passenger-irb --debugger <pid>, everything looks fine. I get the message:
Using Ruby interpreter: /Users/varun/.rvm/wrappers/ruby-1.9.3-p362/ruby
Using rdebug command : /Users/varun/.rvm/gems/ruby-1.9.3-p362/bin/rdebug
*** Attaching debugger to process 55512.
*** Attaching will succeed as soon as process 55512 reaches a 'debugger' call.
*** Press Ctrl-C or Ctrl-D to exit debugger.
So now, I go and refresh any page of my Sinatra app which has a couple of debugger calls for the given route/s. And nothing. I mean the debugger remains where it is, and the request to the route completes without the terminal dropping into the debugger. It's as if the debugger call just wasn't there.