Hide Forgot
Description of problem: We are seeing frequent segfaults in rubygem-addressable when running Aeolus Conductor's cucumber test suite, which indirectly leverages rubygem-addressable while making web requests. /usr/lib/ruby/gems/1.8/gems/addressable-2.2.6/lib/addressable/uri.rb:2148: [BUG] Segmentation fault ruby 1.8.7 (2011-12-28 patchlevel 357) [x86_64-linux] rake aborted! Command failed with status (): [/usr/bin/ruby -S bundle exec cucumber --p...] /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/file_utils.rb:53:in `create_shell_runner' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/file_utils.rb:45:in `call' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/file_utils.rb:45:in `sh' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/file_utils_ext.rb:36:in `sh' /usr/lib/ruby/gems/1.8/gems/cucumber-1.0.1/lib/cucumber/rake/task.rb:104:in `run' /usr/lib/ruby/gems/1.8/gems/cucumber-1.0.1/lib/cucumber/rake/task.rb:193:in `define_task' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:205:in `call' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:205:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:200:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:200:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:158:in `invoke_with_call_chain' /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:151:in `invoke_with_call_chain' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:176:in `invoke_prerequisites' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:174:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:174:in `invoke_prerequisites' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:157:in `invoke_with_call_chain' /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:151:in `invoke_with_call_chain' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:144:in `invoke' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:112:in `invoke_task' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:90:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:90:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:90:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:129:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:84:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:62:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:129:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:59:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/bin/rake:32 /usr/bin/rake:19:in `load' /usr/bin/rake:19 Version-Release number of selected component (if applicable): rubygem-addressable-2.2.6-1.fc15.noarch How reproducible: Frequent but not consistent, perhaps 50% of the time. Steps to Reproduce: I haven't been able to find a simple test case that demonstrates the bug in isolation (yet). It's coming up when running "rake cucumber" in a checkout of git://github.com/aeolusproject/conductor.git (while the tests are in the process of navigating pages).
Found 767648 that may be at least loosely related.
I might suggest to wait until I push the new rubygem.
any ETA on that and/or can you tell me what version of addressable you are pushing? I am getting this error consistently now on f16, with rubygem-addressable-2.2.6-1.fc15.noarch (same as what matt has, just upgraded fedora). If you tell me the version you hope will fix it, I can try installing that locally via gem and see if it helps me at all. Thanks
It's the same version, rubygem-addressable got dropped but its now needed for something else. I'll see if upstream has a patch and add it into the new build. Otherwise, I'll see what I can do for fixing that. <snip code exception> ## # Returns a <code>String</code> representation of the URI object's state. # # @return [String] The URI object's state, as a <code>String</code>. def inspect sprintf("#<%s:%#0x URI:%s>", URI.to_s, self.object_id, self.to_s) end
Shawn, thanks, but it appears to not be (entirely) the fault of addressable. Michal found this blog post, it appears there is a problem with mri ruby itself in how it interacts with gcc, or at least the api it provides for c extensions. This appears to be very bad news: http://timetobleed.com/the-broken-promises-of-mrireeyarv/
It's somewhat possible that this is actually caused by https://bugzilla.redhat.com/show_bug.cgi?id=786231 (a bug in ruby itself). I need to test a little more.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping