-
Bug
-
Resolution: Fixed
-
P3
-
hs23, hs24, hs25, 6, 7, 8
-
installed 64-bit version of Debugging tools for Windows
-
b85
-
generic
-
windows
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8011220 | hs25 | Staffan Larsen | P3 | Resolved | Fixed | b26 |
If 32-bit JVM is running on Windows-x64 host with installed 64-bit version of Debugging tools for Windows, then WindbgDebuggerLocal may throw UnsatisfiedLinkError:
java.lang.UnsatisfiedLinkError: C:\Program Files\Debugging Tools for Windows (x64)\dbghelp.dll: Can't load AMD 64-bit .dll on a IA 32-bit platform
But there could be an appropriate dbghelp.dll in Windows\System32 path.
For 32-bit JVM WindbgDebuggerLocal should avoid path "%SYSTEMROOT%\Program Files\Debugging Tools for Windows (x64)" or at least expect UnsatisfiedLinkError when it load dlls from that place.
See comments for more details.
java.lang.UnsatisfiedLinkError: C:\Program Files\Debugging Tools for Windows (x64)\dbghelp.dll: Can't load AMD 64-bit .dll on a IA 32-bit platform
But there could be an appropriate dbghelp.dll in Windows\System32 path.
For 32-bit JVM WindbgDebuggerLocal should avoid path "%SYSTEMROOT%\Program Files\Debugging Tools for Windows (x64)" or at least expect UnsatisfiedLinkError when it load dlls from that place.
See comments for more details.
- backported by
-
JDK-8011220 WindbgDebuggerLocal should not try to load 64-bit debug libraries for 32-bit JVM
-
- Resolved
-