How we can find -out a dynamic library is corrupted or not?

[Saju Mulakkal Joseph]

How we can find -out a dynamic library is corrupted or not?

[Steven E. Protter]

Shalom,

I use the eyeball method.

I check the size on a similar system with the same OS and patch level.

I do a what on the filename and see the results.

SEP

[Peter Godron]

Hi,
is this a system or user created lib.
If system, have you compared with another system ?

You could try and get all the info out of your shared lib with nm.

The best way to test is to use the individual modules within the library.

Simple stub linking (compile/link without actually calling the module) may produce a first indication of problems (lib modulkes not being found etc.)

Please also read:
http://forums1.itrc.hp.com/service/forums/helptips.do?#33 on how to reward any useful answers given to your questions.

[Saju Mulakkal Joseph]

Thanks for your response, is there any command similar to ldd to find out the correctness of a shared library

[Dennis Handly]

For PA32, you can use:
$ /usr/ccs/bin/odump -verifyall
chatr or ldd
For PA64 and IPF you can use:
$ /usr/ccs/bin/elfdump -n .dynsym -s
$ /usr/ccs/bin/elfdump -S -h -L -o
chatr or ldd

What type of corruption are you looking for?