Boker tov, Thanks for all of your replies that helped me to understand what question I really wanted to ask. So this is a question. I have C++ program which calls many services of third party library.This library is needed only on initialization phase of my program. Linker has resolved symbols of this library and now it is bound to executable and in a run tinethis lib will be mapped will have use count > 0 while executable is in use.I would like to unmap it to release memory, but i do not know how to do it in user space. As an alternative I know that by using dynamic loader calls dlopen() .. dlclose() I can achieve the desired effect The problem that I need to add a lot of dlfind() calls, and I looked for a way dynamic loader can do it.I am not that lazy, but since the code is C++, function names are mangled and I was tring to avoid thisby looking as a subject of this mail said, way to ask kernel to unmap this lib I wish we have __init attribute in a user land ! Many Many Thanks again, Lev. 21.12.2018, 20:18, "Shachar Shemesh" :
On 21/12/2018 16:20, Lev Olshvang
wrote:
Hi All,
I have an executable (C++) which is the exclusive user of the some shared library that it uses only during the initialization phase.
I would like to free memory used by this shared library, because I am running on embedded system.
How can I achieve this?
I know that dlopen() will load shared library, and hope that following dlclose() will free this lib memory.
1. Still I do not know what method should be used to make dynamic linker look again into executable and resolve symbols of the newly appeared symbols ?
2. And how to tell the dynamic linker ld-linux.so to postpone the symbol resolution until dlopen() will load the library?
3. Whether to compile and link executable with this library or leave unresolved symbols?
What you are asking for, as asked, is not possible. If you
explain your use case better, we might better understand what
you're trying to do.
With that said, I think you should just link the library.
All the text segments of the library (i.e. - code) will be loaded
with a read only shared mapping. This means that if they are not
used, they will be unmapped the first time memory becomes
constrained. If you do not use them later on, they will simply not
be loaded to memory. They will still be mapped, but will not load
your embedded system's memory in any significant way.
Shachar
,___Linux-il mailing listLinux-il@cs.huji.ac.ilhttp://mailman.cs.huji.ac.il/mailman/listinfo/linux-il___
Linux-il mailing list
Linux-il@cs.huji.ac.il
http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
