uname.exe Applicaiton Error when running vagrant --version with git bash

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

uname.exe Applicaiton Error when running vagrant --version with git bash

wenlock
Hey,

I ran into an error today when trying out vagrant 1.1 for the first time.  I use vagrant under git bash for typical development model where I want to use git to revision control my vagrant configuration.

I tried doing a vagrant --version immediately after the installation and got a popup from Windows 8, stating uname.exe had an exception and it needed to terminate.

After investigating the event log I found that vagrant comes with an embedded msys-1.0.dll that is different than the msys-1.0.dll that comes with git bash.

After I copied the git bash msys-1.0.dll in the bin directory to the location where the vagrant embedded version , it worked without issues.

I'm guessing there is something that either the git bash or vagrant teams need to do to co-exist better together, just wanted to post so that others who run into the issue are aware and maybe find out if there is a defect that will be fixed for it in the future (maybe the vagrant project has no plans to co-exist :D).

I'm not sure about how bad it is to do the copy of the dll to make them consistent will be but it's much better than it simply not working out of the box.

Thanks

Edward

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: uname.exe Applicaiton Error when running vagrant --version with git bash

Mitchell Hashimoto
Edward,

Interesting, I'm not actually sure what uses msys within Vagrant... maybe the packaged "bsdtar" application. I don't know enough about Windows here to determine the proper course of action. Do you have any ideas?

Best,
Mitchell


On Thu, Mar 14, 2013 at 2:26 PM, mocchi <[hidden email]> wrote:
Hey,

I ran into an error today when trying out vagrant 1.1 for the first time.  I use vagrant under git bash for typical development model where I want to use git to revision control my vagrant configuration.

I tried doing a vagrant --version immediately after the installation and got a popup from Windows 8, stating uname.exe had an exception and it needed to terminate.

After investigating the event log I found that vagrant comes with an embedded msys-1.0.dll that is different than the msys-1.0.dll that comes with git bash.

After I copied the git bash msys-1.0.dll in the bin directory to the location where the vagrant embedded version , it worked without issues.

I'm guessing there is something that either the git bash or vagrant teams need to do to co-exist better together, just wanted to post so that others who run into the issue are aware and maybe find out if there is a defect that will be fixed for it in the future (maybe the vagrant project has no plans to co-exist :D).

I'm not sure about how bad it is to do the copy of the dll to make them consistent will be but it's much better than it simply not working out of the box.

Thanks

Edward

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: uname.exe Applicaiton Error when running vagrant --version with git bash

wenlock
Well I know msys is the POSIX emulator for windows, you likely picked it up from ruby (not sure though).   The version included with vagrant 1.1 happens to be built in 2013, which is more current than the one that came from msysGIT distributables 1.8.1.2.

Unfortunately this might be a dll hell issue with Windows, the shell has the dll loaded, and your dll is getting in the way by getting loaded before theres and causing exe's they deliver like uname.exe to abort.  

Vagrant must be relying on POSIX commands like uname.exe to operate, but without digging into the code, I wouldn't know for sure.   Possibly a longer term fix would be to not rely on POSIX api's for OS native commands.... more coding to support on your end though :<

In anycase, I'll be trying 1.1 some more and dealing with it as a workaround to just sync the dlls on my systems that show up the issue.

Thanks,
Edward



On Thursday, March 14, 2013 2:27:46 PM UTC-7, Mitchell Hashimoto wrote:
Edward,

Interesting, I'm not actually sure what uses msys within Vagrant... maybe the packaged "bsdtar" application. I don't know enough about Windows here to determine the proper course of action. Do you have any ideas?

Best,
Mitchell


On Thu, Mar 14, 2013 at 2:26 PM, mocchi <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="FczaCHvjXIUJ">edward....@...> wrote:
Hey,

I ran into an error today when trying out vagrant 1.1 for the first time.  I use vagrant under git bash for typical development model where I want to use git to revision control my vagrant configuration.

I tried doing a vagrant --version immediately after the installation and got a popup from Windows 8, stating uname.exe had an exception and it needed to terminate.

After investigating the event log I found that vagrant comes with an embedded msys-1.0.dll that is different than the msys-1.0.dll that comes with git bash.

After I copied the git bash msys-1.0.dll in the bin directory to the location where the vagrant embedded version , it worked without issues.

I'm guessing there is something that either the git bash or vagrant teams need to do to co-exist better together, just wanted to post so that others who run into the issue are aware and maybe find out if there is a defect that will be fixed for it in the future (maybe the vagrant project has no plans to co-exist :D).

I'm not sure about how bad it is to do the copy of the dll to make them consistent will be but it's much better than it simply not working out of the box.

Thanks

Edward

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="FczaCHvjXIUJ">vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: uname.exe Applicaiton Error when running vagrant --version with git bash

wenlock
Small, correction, i got this backwards.   The one with vagrant is old,  2011.   The one that comes with git is 2013.

On Thursday, March 14, 2013 2:41:50 PM UTC-7, mocchi wrote:
Well I know msys is the POSIX emulator for windows, you likely picked it up from ruby (not sure though).   The version included with vagrant 1.1 happens to be built in 2013, which is more current than the one that came from msysGIT distributables 1.8.1.2.

Unfortunately this might be a dll hell issue with Windows, the shell has the dll loaded, and your dll is getting in the way by getting loaded before theres and causing exe's they deliver like uname.exe to abort.  

Vagrant must be relying on POSIX commands like uname.exe to operate, but without digging into the code, I wouldn't know for sure.   Possibly a longer term fix would be to not rely on POSIX api's for OS native commands.... more coding to support on your end though :<

In anycase, I'll be trying 1.1 some more and dealing with it as a workaround to just sync the dlls on my systems that show up the issue.

Thanks,
Edward



On Thursday, March 14, 2013 2:27:46 PM UTC-7, Mitchell Hashimoto wrote:
Edward,

Interesting, I'm not actually sure what uses msys within Vagrant... maybe the packaged "bsdtar" application. I don't know enough about Windows here to determine the proper course of action. Do you have any ideas?

Best,
Mitchell


On Thu, Mar 14, 2013 at 2:26 PM, mocchi <[hidden email]> wrote:
Hey,

I ran into an error today when trying out vagrant 1.1 for the first time.  I use vagrant under git bash for typical development model where I want to use git to revision control my vagrant configuration.

I tried doing a vagrant --version immediately after the installation and got a popup from Windows 8, stating uname.exe had an exception and it needed to terminate.

After investigating the event log I found that vagrant comes with an embedded msys-1.0.dll that is different than the msys-1.0.dll that comes with git bash.

After I copied the git bash msys-1.0.dll in the bin directory to the location where the vagrant embedded version , it worked without issues.

I'm guessing there is something that either the git bash or vagrant teams need to do to co-exist better together, just wanted to post so that others who run into the issue are aware and maybe find out if there is a defect that will be fixed for it in the future (maybe the vagrant project has no plans to co-exist :D).

I'm not sure about how bad it is to do the copy of the dll to make them consistent will be but it's much better than it simply not working out of the box.

Thanks

Edward

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: uname.exe Applicaiton Error when running vagrant --version with git bash

wenlock
OK, learning more on how vagrant works under the hood helped me find a much cleaner workaround, which i think is better for vagrant dependencies too.

Since I'm in a shell environment on git bash, vagrant uses a bash script in the bin directory to bootstrap the ruby execute command that it will need.

I moved line 56 in bin/vagrant to occur before line 44 (which is where the PATH= is redifined to help with pointing to the embedded_dir folder that is in conflict with the git bash libraries.).  Line 56 is making a call to uname -o to get the OS type so it can run some cygpath commands for ux to windows conversion, which im guessing git bash isn't needing because it deals better (maybe??).

In anycase, fresh install vagrant --version works in git bash now.

I'll have to do more testing to see if something else breaks.

Thanks,
Edward

On Thursday, March 14, 2013 8:19:02 PM UTC-7, mocchi wrote:
Small, correction, i got this backwards.   The one with vagrant is old,  2011.   The one that comes with git is 2013.

On Thursday, March 14, 2013 2:41:50 PM UTC-7, mocchi wrote:
Well I know msys is the POSIX emulator for windows, you likely picked it up from ruby (not sure though).   The version included with vagrant 1.1 happens to be built in 2013, which is more current than the one that came from msysGIT distributables 1.8.1.2.

Unfortunately this might be a dll hell issue with Windows, the shell has the dll loaded, and your dll is getting in the way by getting loaded before theres and causing exe's they deliver like uname.exe to abort.  

Vagrant must be relying on POSIX commands like uname.exe to operate, but without digging into the code, I wouldn't know for sure.   Possibly a longer term fix would be to not rely on POSIX api's for OS native commands.... more coding to support on your end though :<

In anycase, I'll be trying 1.1 some more and dealing with it as a workaround to just sync the dlls on my systems that show up the issue.

Thanks,
Edward



On Thursday, March 14, 2013 2:27:46 PM UTC-7, Mitchell Hashimoto wrote:
Edward,

Interesting, I'm not actually sure what uses msys within Vagrant... maybe the packaged "bsdtar" application. I don't know enough about Windows here to determine the proper course of action. Do you have any ideas?

Best,
Mitchell


On Thu, Mar 14, 2013 at 2:26 PM, mocchi <[hidden email]> wrote:
Hey,

I ran into an error today when trying out vagrant 1.1 for the first time.  I use vagrant under git bash for typical development model where I want to use git to revision control my vagrant configuration.

I tried doing a vagrant --version immediately after the installation and got a popup from Windows 8, stating uname.exe had an exception and it needed to terminate.

After investigating the event log I found that vagrant comes with an embedded msys-1.0.dll that is different than the msys-1.0.dll that comes with git bash.

After I copied the git bash msys-1.0.dll in the bin directory to the location where the vagrant embedded version , it worked without issues.

I'm guessing there is something that either the git bash or vagrant teams need to do to co-exist better together, just wanted to post so that others who run into the issue are aware and maybe find out if there is a defect that will be fixed for it in the future (maybe the vagrant project has no plans to co-exist :D).

I'm not sure about how bad it is to do the copy of the dll to make them consistent will be but it's much better than it simply not working out of the box.

Thanks

Edward

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: uname.exe Applicaiton Error when running vagrant --version with git bash

Mitchell Hashimoto
Edward,

Thanks so much!

Ah hah. I fixed that now and will release a new Windows installer in the next day or two that fixes this permanently.

Thanks,
Mitchell


On Fri, Mar 15, 2013 at 11:23 AM, mocchi <[hidden email]> wrote:
OK, learning more on how vagrant works under the hood helped me find a much cleaner workaround, which i think is better for vagrant dependencies too.

Since I'm in a shell environment on git bash, vagrant uses a bash script in the bin directory to bootstrap the ruby execute command that it will need.

I moved line 56 in bin/vagrant to occur before line 44 (which is where the PATH= is redifined to help with pointing to the embedded_dir folder that is in conflict with the git bash libraries.).  Line 56 is making a call to uname -o to get the OS type so it can run some cygpath commands for ux to windows conversion, which im guessing git bash isn't needing because it deals better (maybe??).

In anycase, fresh install vagrant --version works in git bash now.

I'll have to do more testing to see if something else breaks.

Thanks,
Edward


On Thursday, March 14, 2013 8:19:02 PM UTC-7, mocchi wrote:
Small, correction, i got this backwards.   The one with vagrant is old,  2011.   The one that comes with git is 2013.

On Thursday, March 14, 2013 2:41:50 PM UTC-7, mocchi wrote:
Well I know msys is the POSIX emulator for windows, you likely picked it up from ruby (not sure though).   The version included with vagrant 1.1 happens to be built in 2013, which is more current than the one that came from msysGIT distributables 1.8.1.2.

Unfortunately this might be a dll hell issue with Windows, the shell has the dll loaded, and your dll is getting in the way by getting loaded before theres and causing exe's they deliver like uname.exe to abort.  

Vagrant must be relying on POSIX commands like uname.exe to operate, but without digging into the code, I wouldn't know for sure.   Possibly a longer term fix would be to not rely on POSIX api's for OS native commands.... more coding to support on your end though :<

In anycase, I'll be trying 1.1 some more and dealing with it as a workaround to just sync the dlls on my systems that show up the issue.

Thanks,
Edward



On Thursday, March 14, 2013 2:27:46 PM UTC-7, Mitchell Hashimoto wrote:
Edward,

Interesting, I'm not actually sure what uses msys within Vagrant... maybe the packaged "bsdtar" application. I don't know enough about Windows here to determine the proper course of action. Do you have any ideas?

Best,
Mitchell


On Thu, Mar 14, 2013 at 2:26 PM, mocchi <[hidden email]> wrote:
Hey,

I ran into an error today when trying out vagrant 1.1 for the first time.  I use vagrant under git bash for typical development model where I want to use git to revision control my vagrant configuration.

I tried doing a vagrant --version immediately after the installation and got a popup from Windows 8, stating uname.exe had an exception and it needed to terminate.

After investigating the event log I found that vagrant comes with an embedded msys-1.0.dll that is different than the msys-1.0.dll that comes with git bash.

After I copied the git bash msys-1.0.dll in the bin directory to the location where the vagrant embedded version , it worked without issues.

I'm guessing there is something that either the git bash or vagrant teams need to do to co-exist better together, just wanted to post so that others who run into the issue are aware and maybe find out if there is a defect that will be fixed for it in the future (maybe the vagrant project has no plans to co-exist :D).

I'm not sure about how bad it is to do the copy of the dll to make them consistent will be but it's much better than it simply not working out of the box.

Thanks

Edward

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.