code_junkie

Are there any tools for checking symbols in cross compiled .so files?

Nov 12th, 2011
63
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.42 KB | None | 0 0
  1. --no-undefined
  2. Report unresolved symbol references from regular object files.
  3. This is done even if the linker is creating a non-symbolic shared
  4. library. The switch --[no-]allow-shlib-undefined controls the
  5. behaviour for reporting unresolved references found in shared
  6. libraries being linked in.
  7.  
  8. --allow-shlib-undefined
  9. --no-allow-shlib-undefined
  10. Allows (the default) or disallows undefined symbols in shared
  11. libraries. This switch is similar to --no-undefined except
  12. that it determines the behaviour when the undefined symbols are
  13. in a shared library rather than a regular object file. It does
  14. not affect how undefined symbols in regular object files are
  15. handled.
  16.  
  17. The reason that --allow-shlib-undefined is the default is that the
  18. shared library being specified at link time may not be the
  19. same as the one that is available at load time, so the symbols might
  20. actually be resolvable at load time. Plus there are some systems,
  21. (eg BeOS) where undefined symbols in shared libraries is normal.
  22. (The kernel patches them at load time to select which function is most
  23. appropriate for the current architecture. This is used for example to
  24. dynamically select an appropriate memset function). Apparently it is
  25. also normal for HPPA shared libraries to have undefined symbols.
Add Comment
Please, Sign In to add comment