title: tracking origin of symbols in shared libraries
body: <p>I have a shared library (more specificly a native python module) which references some symbols from other libraries. <code>ldd -r</code> displays which symbols of the library can't be resolved dynamically on the system. example:</p>
  
  <pre><code># ldd -r /usr/lib/python3.4/site-packages/_selinux.cpython-34m.so
  …
  undefined symbol: selabel_digest        (/usr/lib/python3.4/site-packages/_selinux.cpython-34m.so)
  </code></pre>
  
  <p>Now I have a similar system where the linking seems to work, ldd doesn't report any unresolved symbols.<br>
  <strong>How can I track how and from which sources (filename of the shared library) certain symbols are resolved on that system?</strong> I hope this might help me to get the linking on the first system correct.</p>