| 1 |
On 01/17/2011 12:22 AM, Helmut Jarausch wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> on one of my machines, googleearth crashes. An |
| 5 |
> ldd /opt/googleearth/googleearth.bin | grep crypto |
| 6 |
> shows that it tries to load both |
| 7 |
> /usr/lib32/libcrypto.so.0.9.8 and /usr/lib32/libcrypto.so.1.0.0 |
| 8 |
> |
| 9 |
> |
| 10 |
> On a different machine it only loads /usr/lib32/libcrypto.so.1.0.0 |
| 11 |
> and does not crash. |
| 12 |
> |
| 13 |
> So, how can I find out the tree of dynamic libraries. |
| 14 |
> Probably these dynamic libraries are not loaded directly but |
| 15 |
> indirectly by some other dynamic library. |
| 16 |
> |
| 17 |
> Is there anything better than invoking ldd for each dynamic library |
| 18 |
> which is loaded by an application to see how it got loaded? |
| 19 |
|
| 20 |
Good question, and maybe someone has a better idea than mine, but I |
| 21 |
just grep through the entire library directory until I find the name |
| 22 |
of the old library: |
| 23 |
|
| 24 |
# grep -r libcrypto.so.0 /usr/lib32/* |
| 25 |
Binary file /usr/lib32/libcrypto.so.0.9.8 matches |
| 26 |
Binary file /usr/lib32/libssl.so.0.9.8 matches |
| 27 |
|
| 28 |
You may find at least one other library that matches. I'd do the |
| 29 |
same grep through /usr/bin and /usr/lib64 also. |
Archives