astashov
Debugger doesn't seem to work when workling is being used.
Not sure if this is a bug or an FYI. My app makes use of workling and starling to do async processing. It seem some part of this debugger stack is doesn't work if a workling process is being used.
I started the debugger with :Rdebugger and set a breakpoint in a controller with \b, The line was highlighted in red. The ruby_debugger_log indicated the break point was set. I refreshed the web page, but the app didn't break at the breakpoint.
In my ruby_debugger_log: cat ruby_debugger_log
2009/06/10 11:20:47 Start debugger
2009/06/10 11:21:38 Set breakpoint to: /home/scott/git/RepgenDataLoader/app/controllers/database_controller.rb:108
2009/06/10 11:21:56 Set breakpoint to: /home/scott/git/RepgenDataLoader/app/controllers/database_controller.rb:5
There must be some kind of workling incompatibility. I noticed this odd thing: After I start the debugger netstat shows the debugger listening) (note that I modifed the debugger to listen on 39997 and 39998): tcp 0 0 127.0.0.1:39997 0.0.0.0:* LISTEN 25586/ruby1.8 tcp 0 0 127.0.0.1:39998 0.0.0.0:* LISTEN 25589/ruby
After I stop the debugger using :RdbStop netstat shows this: tcp 0 0 127.0.0.1:39997 0.0.0.0:* LISTEN 25634/workling
Workling seems to have take over the debugger port. Very strange.
I cannot start the debugger because workling is listening on the debugger port. No matter what port I start the debugger on this seems to happen. I need to kill the workling process.
When I don't start my workling/starling processes the debugger works fine.
Really, pretty strange. Unfortunately, I don't have experience with workling/starling, never used them with/without debugger. I even don't know how I can help you, sorry...
If you find reason of this strange behaviour, I'll be happy if you send me patch, or just explanation of this bug :). Anyway, thanks for this issue, I'll leave it here unclosed.
