Issue #2404 has been updated by Wayne E. Seguin.


This bug is now present and highly invasive in the newly released 1.9.1-p429

    ??? ruby -v
    ruby 1.9.1p429 (2010-07-02 revision 28523) [x86_64-linux]

    ??? gem --version 
    Error loading gem paths on load path in gem_prelude
    can't modify frozen string
    <internal:gem_prelude>:69:in `force_encoding'
    <internal:gem_prelude>:69:in `set_home'
    <internal:gem_prelude>:38:in `dir'
    <internal:gem_prelude>:76:in `set_paths'
    <internal:gem_prelude>:47:in `path'
    <internal:gem_prelude>:286:in `push_all_highest_version_gems_on_load_path'
    <internal:gem_prelude>:355:in `<compiled>'
    1.3.7

    ??? irb
    Error loading gem paths on load path in gem_prelude
    can't modify frozen string
    <internal:gem_prelude>:69:in `force_encoding'
    <internal:gem_prelude>:69:in `set_home'
    <internal:gem_prelude>:38:in `dir'
    <internal:gem_prelude>:76:in `set_paths'
    <internal:gem_prelude>:47:in `path'
    <internal:gem_prelude>:286:in `push_all_highest_version_gems_on_load_path'
    <internal:gem_prelude>:355:in `<compiled>'
    ruby-1.9.1-p429 > 

Whereas on the exact same host, same installation method (RVM):

??? ruby -v
ruby 1.9.1p378 (2010-01-10 revision 26273) [x86_64-linux]

??? gem --version 
1.3.6
??? irb
ruby-1.9.1-p378 > 

I am able to reproduce on my local as well as the server listed above.
Simply installing p429 triggers the bug.


----------------------------------------
http://redmine.ruby-lang.org/issues/show/2404

----------------------------------------
http://redmine.ruby-lang.org