Here is a unobtrusive workaround using the documented capabilities of URI: ~~~ ruby module URI DEFAULT_PARSER = Parser.new(:HOSTNAME => "(?:(?:[a-zA-Z\\d](?:[-\\_a-zA-Z\\d]*[a-zA-Z\\d])?)\\.)*(?:[a-zA-Z](?:[-\\_a-zA-Z\\d]*[a-zA-Z\...coldnebo (Larry Kyrala)
The URI abstraction speaks to RFC3986 (DNS) more directly than RFC952 (hostnames). The confusion is understandable. Still, standards-based systems exist right now that allow this (e.g. we have an nginx deployed application that chose...coldnebo (Larry Kyrala)
Cool. Both of our segfault locations in ruby code suggest some kind of buffer sizing problem (mine segs on read, yours on write). Looking at the two locations where the segfault occurs: /local/rvm/rubies/ruby-1.9.2-p318/lib/ruby/1....coldnebo (Larry Kyrala)
Ok, running that without the debugger gives a better error: /local/rvm/rubies/ruby-1.9.2-p318/lib/ruby/1.9.1/net/imap.rb:1099:in `get_tagged_response': STORE attempt on READ-ONLY folder (Failure) (Net::IMAP::NoResponseError) from...coldnebo (Larry Kyrala)
Ok, I think I have a test case for you Martin... I was able to reproduce this again Google's IMAP server, so I created a dummy test account and a simple test case. Note: it only segfaults when in debug, I have no idea why? (is the debug...coldnebo (Larry Kyrala)
trying again pointing at openssl dir to see if that makes a difference: $ rvm reinstall 1.9.2 --with-openssl-dir=/usr/include/openssl nope, same seg fault. coldnebo (Larry Kyrala)
This also happens in 1.9.2-p318: While using the mail gem (http://rubygems.org/gems/mail) in a ruby-debug19 context: 85 emails = Mail.find(:mailbox => opts[:mailbox], :keys => ["ALL", "UNSEEN"], :count => 9999) do |email, ima...coldnebo (Larry Kyrala)
coldnebo (Larry Kyrala)09:16 PM Ruby Bug #8241: If uri host-part has underscore ( '_' ), 'URI#parse' raise 'URI::InvalidURIError'