If I use System Monitor and look-up memory maps for an application there are plenty of files with the so extension. I assumed that Libraries where huge but it you open them up they are a small (under 50) lines of binary code , hardly a library. So my thinking is that the so address are segments of a bigger library. This is not logical either.

I have browsed a few guides but could I get an overview to jumpstart a better understanding?

Thanks in advacance!

A line of binary sounds like a seriously misleading, inaccurate, basically meaningless measure. I don't know what you think you're measuring, but I expect you're misinterpreting the results.

You might want to look at the file size of the .so file. If you want more details about internal sizes, you need to use a tool that understands the file format.

I don't know what you even mean by "so addresses" but whatever you mean, I'm pretty sure you're right that it also isn't logical.

Too broad a topic.

I have seen some good tutorials on various aspects of constructing useful .so files. If you want a true understanding of .so files, you have to look from that point of view, but I expect you aren't ready for that level of detail.

I have no clue what kind of info about .so files might be understandable but also satisfy your curiosity.

1 members found this post helpful.

I doubt the kernel makes a permanent file for segments of a shared library ,but I really would like to know. In my opinion Memory Mapping and Shared Library documentation is the most neglected. I'm currently reading this one.http://www.ibm.com/developerworks/li...ibs/index.html

Attached Thumbnails