I've seen a lot of messages on ###@###.### where developers
complain that they are getting UnsatisfiedLinkErrors when they
really shouldn't be. It is usually the case that there was a
problem loading one of the dependent libraries. I tell them
about LD_DEBUG, and then they get back saying "yep LD_DEBUG
exposed a problem in my library, but why didn't the
UnsatisfiedLinkError tell me so in the first place?"

For instance, if you do System.loadLibrary("awt"), and there
was no libXm.so is your LD_LIBRARY_PATH or in libawt.so's
-Rpaths, then the message in the exception is "awt not found
in shared library path". It would be better to say
"can not load awt: libXm.so file not found."

This should be easy to do on Solaris by propogating dlerror()
out through the HPI into the VM. Dunno what the equivalent
is in Win32, but I'd guess GetLastError().

Also check that UnsatisifiedLinkErrors for symbols not found
(dynoLink?) report sensible error messages as well.

anand.palaniswamy@Eng 1998-09-03