New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jline on Windows does not check that %TEMP%\jansi.dll is correct for JVM bit model #4703
Comments
Imported From: https://issues.scala-lang.org/browse/SI-4703?orig=1 |
huynhjl said: |
@paulp said: |
Hiram Chirino (chirino) said: |
huynhjl said: |
@paulp said: |
huynhjl said: |
@paulp said: |
Henning Hoefer (hho) said: I'm asking, since this doesn't seem to be fixed in 2.9.1.final -- if I switch between a 32- and a 64-bit-JDK I always get the "Failed to created JLineReader"... |
huynhjl said (edited on Dec 20, 2011 3:22:03 PM UTC): |
There are two jansi.dll bundled in jline.jar, one for 32 bits and one for 64 bits. The one being picked up is chosen based on the value of sun.arch.data.model system property (32 or 64). Once unpacked the dll does not get refreshed. The only check that is performed is based on timestamp of jline.jar and jansi.dll. Running first the 32 bits version unpacks the 32 bits dll. When starting the 64 bits JVM, jansi.dll is then incompatible. (or vice versa if starting with 64 bits).
The bug is really in the hawtjni dependent library used by jline.
Here is a cygwin session demonstrating the issue:
For the end user, the work around is to delete the dll
del %TEMP%\jansi.dll
.The text was updated successfully, but these errors were encountered: