Hi again guys,
2 things.. Noticed a significant performance increase going from the 209 to the 403 EAP release. Nice work! It's a little slow to start up and finish running the background processes on initialisation but once that's done it does seem significantly more fluent!
Found a bug though. When the debugger starts I now see 2 seperate windows ruby.exe processes starting in my task manager. Most times one of these processes will die off pretty quickly and so won't cause any problems. But occassionally.. like 1 in 5 times, both processes stay open and when I close the debugger using the square "Stop" button in the actual debugger window at the bottom only one of these processes is killed off and I then have to forcefully go into the task manager and kill off the other process before I can begin a new debugging session. Otherwise when I try and start a new debugging session I keep seeing this error:
Fast Debugger (ruby-debug-ide 0.4.17.beta8, ruby-debug-base 0.11.30.pre2) listens on 127.0.0.1:65180
Fatal exception in DebugThread loop: Only one usage of each socket address (protocol/network address/port) is normally permitted. - bind(2)
from: C:/ruby192/lib/ruby/gems/1.9.1/gems/ruby-debug-ide-0.4.17.beta8/lib/ruby-debug-ide.rb:150:in `new'
from: C:/ruby192/lib/ruby/gems/1.9.1/gems/ruby-debug-ide-0.4.17.beta8/lib/ruby-debug-ide.rb:150:in `block in start_control
This happens running Ruby192 with the latest debugger gems but also with Ruby 186 using really old debugger gems (ruby-debug-base 0.9.3 and the ruby-debug-ide 0.1.9) so I don't think it's being caused by any of the ruby-debug gems themselves.. but I could be wrong.
Anyways, cheers guys. All the best