md5.so/sha1.so loaderror on `gem help command` and `bundler` both error on Win7 64 with 1.9.3-p0, work fine with 1.9.2-p290

[nomoon]

I at first thought this might be a problem with rubygems, or with bundler, but the custom_require method seems fine, as I'll show below. I've posted it around

Typing bundle command gives the following error:

C:/Dev/Ruby193/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require': 193: %1 is not a valid Win32 application.   - C:/Dev/Ruby193/lib/ruby/1.9.1/i386-mingw32/digest/sha1.so (LoadError)
        from C:/Dev/Ruby193/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
        from C:/Dev/Ruby193/lib/ruby/gems/1.9.1/gems/bundler-1.0.22/lib/bundler/definition.rb:1:in `<top (required)>'
        from C:/Dev/Ruby193/lib/ruby/gems/1.9.1/gems/bundler-1.0.22/lib/bundler.rb:138:in `definition'
        from C:/Dev/Ruby193/lib/ruby/gems/1.9.1/gems/bundler-1.0.22/lib/bundler/cli.rb:219:in `install'
        from C:/Dev/Ruby193/lib/ruby/gems/1.9.1/gems/bundler-1.0.22/lib/bundler/vendor/thor/task.rb:22:in `run'
        from C:/Dev/Ruby193/lib/ruby/gems/1.9.1/gems/bundler-1.0.22/lib/bundler/vendor/thor/invocation.rb:118:in `invoke_task'
        from C:/Dev/Ruby193/lib/ruby/gems/1.9.1/gems/bundler-1.0.22/lib/bundler/vendor/thor.rb:263:in `dispatch'
        from C:/Dev/Ruby193/lib/ruby/gems/1.9.1/gems/bundler-1.0.22/lib/bundler/vendor/thor/base.rb:386:in `start'
        from C:/Dev/Ruby193/lib/ruby/gems/1.9.1/gems/bundler-1.0.22/bin/bundle:13:in `<top (required)>'
        from C:/Dev/Ruby193/bin/bundle:19:in `load'
        from C:/Dev/Ruby193/bin/bundle:19:in `<main>'

I tracked this to the line require "digest/sha1 at the top of bundler-1.0.22/lib/bundler/definition.rb but that looks odd. So I tried something to reproduce the problem.

The following file executes fine:

require "digest/sha1"
puts Digest::SHA1.hexdigest('Test')

but this slight modification throws an error:

require "bundler"
require "digest/sha1"
puts Digest::SHA1.hexdigest('Test')

C:/Dev/Ruby193/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require': 193: %1 is not a valid Win32 application.   - C:/Dev/Ruby193/lib/ruby/1.9.1/i386-mingw32/digest/sha1.so (LoadError)
        from C:/Dev/Ruby193/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
        from digesttest.rb:4:in `<main>'

to make matters weirder, this also works fine:

require "rails"
require "bundler"
require "digest/sha1"
puts Digest::SHA1.hexdigest('Test')

However, requiring "bundler" before "rails" causes the same custom_require failure.

To prove this isn't a bundler-only issue, when I run gem help commands I get this error:

ERROR:  Loading command: server (LoadError)
    193: %1 is not a valid Win32 application.   - C:/Dev/Ruby193/lib/ruby/1.9.1/i386-mingw32/digest/md5.so
ERROR:  While executing gem ... (NameError)
    uninitialized constant Gem::Commands::ServerCommand

[luislavena]

Where you obtained RubyInstaller 1.9.3-p0?

Do you have any antivirus software installed? Asking this because extensions provided as part of Ruby are valid applications unless you don't have WoW64 installed (something that is part of Windows x64) or you have DEP enabled.

https://github.com/oneclick/rubyinstaller/wiki/Troubleshooting#wiki-dep_segfault

[nomoon]

I downloaded 1.9.3 from the rubyinstaller.org. As noted in the bug, the md5 and sha1 modules will load under most normal circumstances. Something in those gems' code seems to change this, however, though only on this particular version/platform of Ruby. I'm running 1.9.3-p0 with the same gem versions on my Macbook with no problems.

Thanks for the FAQ link. I'm going to try that.

[nomoon]

Ok, so I fixed it, but the fix is very weird.

I'm running FRAPS (a framerate and DirectX/openGL screen-recording utility), and whenever it is running, this error is present. As soon as I quit the program, everything is fine.

I can only guess that FRAPS is trolling for some hook that loading these .so files appears to trigger.

[luislavena]

Is normal for those modules to be loaded, what is not normal is you receiving the error of these being invalid win32 application, which can lead to a corrupt installation or something that is blocking the modules from being loaded.

The comparison against OSX is pointless: the operating systems and their layers are completely different so that it worked on OSX does not say anything.

I've Windows 7 x64 Ultimate with Ruby 1.9.3-p0 and works perfectly. I use the same packages as the installer because I built the installers

Please check the Troubleshooting link I provided and also respond to us what AV software you have installed.

If required, please download the 7zip package and:

• Extract it into a new folder
• Open a new command prompt
• Adjust the PATH to it (SET PATH=C:\extrated-ruby193\bin;%PATH%)
• And try: `ruby -v -e "require 'digest/md5'"

Most likely there is a AV software affecting your machine, DEP protection or there is a DLL conflict that is blocking extension from being loaded.

On your response, please include the current value of PATH (SET PATH) which will help us figure out what is wrong.

Thank you.

[luislavena]

I'm running FRAPS (a framerate and DirectX/openGL screen-recording utility), and whenever it is running, this error is present. As soon as I quit the program, everything is fine.

FRAPS and other tools add hooks that replace normal LoadLibrary behavior and affect loading of extensions.

[luislavena]

Closing this out as being a 3rd party issue.

Please let Bundler guys know about this (and close your report there too).

Thank you.

[rdp]

maybe tell the FRAPS guys too...

[nomoon]

Yup. I let them know.

[zh4ngx]

Want to confirm that FRAPS was indeed the issue for me as well (and this was tough to Google!)

[KaiStarkk]

Was also the issue for me. Thanks a bunch for the fix, that took a while to find!!

[thegrok]

nomoon thank you so much for discovering it's FRAPS, been banging my head against the wall for almost three hours.

[zh4ngx]

Way too many other annoying problems w/windows, so I'm already off of it :). Try fixing the libv8 problems :)

[luislavena]

@ZhangBanger

Is not our responsability fix every single gem out there. Is much better use NodeJS externally than using therubyracer and libv8 that eats a lot of memory (and used to segfault).

[zh4ngx]

Oh, wasn't saying that at all. Actually recommending that people switch to
Linux in general, because there are fewer problems that remain unfixed. :)
On May 12, 2012 5:07 AM, "Luis Lavena" <
reply@reply.github.com>
wrote:

@ZhangBanger

Is not our responsability fix every single gem out there. Is much better
use NodeJS externally than using therubyracer and libv8 that eats a lot of
memory (and used to segfault).

---

Reply to this email directly or view it on GitHub:
#102 (comment)