Unsatisfied code symbol error even when the libs have the definition,

[Raghava_1]

Hi,

We have two shared libraries a.so and b.so. b.so currently has a new function which is referred in a.so. When system tries loading a.so, it throws an 'Unsatisfied code symbol '' in load module /a.so'. We are sure that b.so has the function and is in PATH/LD_LIBRARY_PATH. Confirmed by running the shared obj through strings too.

This, however goes through without an issue in another deployment, with no changes to anything.

What could be a possible reason for this issue? Please let me know if such an issue (&& possibly its solution) is encountered anywhere.

TIA!

PS: We even copied a.so and b.so from instance where things are fine, and when checked in the buggy area, it still fails. We are sure that the proper shared libs are in PATH/LD_LIBRARY_PATH/SHLIB_PATH and LIBPATH. cksum match is done.

[Dennis Handly · Accepted solution]

>When system tries loading a.so

How is a.so referring to b.so?

>Confirmed by running the shared lib through strings too.

The only tool for doing this is "elfdump -n .dynsym -s".

>We even copied a.so and b.so from instance where things are fine

Have you made sure you have the same dld patches on both systems?