-
Bug
-
Resolution: Fixed
-
P3
-
6
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2176862 | 7 | Ivan Krylov | P3 | Closed | Fixed | b10 |
JDK-2146252 | 5.0u14 | Ivan Krylov | P3 | Closed | Fixed | b01 |
JDK-2146341 | hs10 | Ivan Krylov | P3 | Closed | Fixed | b10 |
While reading forums I've tripped across several users who are rightly confused UnsatisfiedLinkErrors of the form:
Exception in thread "Thread-1" java.lang.UnsatisfiedLinkError: /home/ktasinga/development/aperi/AperiDebug/lib/linux-ix86/libDataServer.so: Can't load IA 32-bit .so on a IA 32-bit platform
instead of the infinitely more helpful:
Exception in thread "Thread-1" java.lang.UnsatisfiedLinkError: /home/ktasinga/development/aperi/AperiDebug/lib/linux-ix86/libDataServer.so: /home/ktasinga/development/aperi/AperiDebug/lib/linux-ix86/libDataServer.so: undefined symbol: adminGIDField
The code added to fix 6374419 suppresses the real error message from the linker in this case. That could should probably only trigger if the library and the platform are different. Given that we went to the trouble to backport this to an 1.5 update release this should also be fixed in a 1.5 update release.
Here are two cases where users on our forums were confused by this message
http://forum.java.sun.com/thread.jspa?threadID=792436
http://forum.java.sun.com/thread.jspa?threadID=5126164
Exception in thread "Thread-1" java.lang.UnsatisfiedLinkError: /home/ktasinga/development/aperi/AperiDebug/lib/linux-ix86/libDataServer.so: Can't load IA 32-bit .so on a IA 32-bit platform
instead of the infinitely more helpful:
Exception in thread "Thread-1" java.lang.UnsatisfiedLinkError: /home/ktasinga/development/aperi/AperiDebug/lib/linux-ix86/libDataServer.so: /home/ktasinga/development/aperi/AperiDebug/lib/linux-ix86/libDataServer.so: undefined symbol: adminGIDField
The code added to fix 6374419 suppresses the real error message from the linker in this case. That could should probably only trigger if the library and the platform are different. Given that we went to the trouble to backport this to an 1.5 update release this should also be fixed in a 1.5 update release.
Here are two cases where users on our forums were confused by this message
http://forum.java.sun.com/thread.jspa?threadID=792436
http://forum.java.sun.com/thread.jspa?threadID=5126164
- backported by
-
JDK-2146252 fix for 6374419 suppresses real error message from the linker
- Closed
-
JDK-2146341 fix for 6374419 suppresses real error message from the linker
- Closed
-
JDK-2176862 fix for 6374419 suppresses real error message from the linker
- Closed
- relates to
-
JDK-6374419 Misleading error message if 32bit dll used together with 64 bit VM
- Closed
-
JDK-2136684 Misleading error message if 32bit dll used together with 64 bit VM
- Closed