These days rpm installs most libs stripped of their symbols, which is fine as it makes them smaller and presumably load faster.
But how does the linker resolve symbols against stripped libs? And if the linker can do it, why can't /usr/bin/nm ?
John
Hello, John Ellson napsal(a):
These days rpm installs most libs stripped of their symbols, which is fine as it makes them smaller and presumably load faster.
But how does the linker resolve symbols against stripped libs? And if the linker can do it, why can't /usr/bin/nm ?
There are two types of symbol information: - ELF symbols, used for linking (both static and dynamic) - debugging information, used only by the debugger.
strip and nm works on debugging information, not ELF symbols. You can use e.g. readelf to see the ELF symbols. Mirek
On Sat, 2006-04-29 at 10:44 -0400, John Ellson wrote:
These days rpm installs most libs stripped of their symbols, which is fine as it makes them smaller and presumably load faster.
But how does the linker resolve symbols against stripped libs? And if the linker can do it, why can't /usr/bin/nm ?
just pass -D to nm... or use eu-readelf ;)
Arjan van de Ven wrote:
On Sat, 2006-04-29 at 10:44 -0400, John Ellson wrote:
These days rpm installs most libs stripped of their symbols, which is fine as it makes them smaller and presumably load faster.
But how does the linker resolve symbols against stripped libs? And if the linker can do it, why can't /usr/bin/nm ?
just pass -D to nm... or use eu-readelf ;)
Remind me why we don't make the useful behaviour for nm the default.
- ajax
devel@lists.stg.fedoraproject.org
-
Adam Jackson -
Arjan van de Ven -
John Ellson -
Miloslav Trmač