=begin On Thu, Apr 22, 2010 at 6:58 PM, Yusuke ENDOH <mame@tsg.ne.jp> wrote: > This may be side effect of ipv6 support of ext/socket. > What's printed by: > > require "socket" > p TCPServer.new("localhost", 1234).addr > p TCPSe...orem (Chris Schlaeger)
=begin I did some more tests and the problem is most likely not DRb specific. I can reproduce this with TCPSocket as well. The system was an openSUSE 11.1 and 11.2. Both have IPv6 enabled. The problem does not occur when I use 127.0....orem (Chris Schlaeger)
=begin When I call DRb.start_service('druby://localhost:1234') and port 1234 is already in use, I silently end up with a broken DRb service. start_service should detect that the port is already in use and raise an exception.
=begin During the development of a project management application I encountered the following problem. Every 10th run or so, the ruby interpreter crashes with the error message in the subject. I've attached a full backtrace in the log f...orem (Chris Schlaeger)
=begin Yes, I was using Ruby 1.9.1 (or rather a post 1.9.1 SVN snapshot).
Chris
On Mon, Mar 9, 2009 at 8:00 AM, Charlie Savage <redmine@ruby-lang.org> wrote: > Issue #1227 has been updated by Charlie Savage. > > > Hey Chris, ...orem (Chris Schlaeger)
=begin I'm trying to profile sections of a large application (taskjuggler) with ruby-prof. As soon as I hit the RubyProf.stop call, I get the attached error message. Since ruby-prof is using C code as well, this may be a ruby-prof issue...orem (Chris Schlaeger)
=begin I've tried to run taskjuggler with ruby 1.9 CVS from today and got internal error messages. The applications runs fine with ruby 1.8.7. I tried to cut it down to a smaller test case, but it seems like you need the full app to tri...orem (Chris Schlaeger)
orem (Chris Schlaeger)02:33 AM Ruby Bug #3052: DRb::start_service fails to detect used port