This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug dynamic-link/21427] Leak memory in dlsym(), and take double library files


https://sourceware.org/bugzilla/show_bug.cgi?id=21427

Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adhemerval.zanella at linaro dot o
                   |                            |rg

--- Comment #1 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
These are allocation which are handle by loader cache and only shown in
valgrind with the '--show-reachable=yes'.  Since they are cached for the
application, it is expected that loader maintains lingering pointers to the
data and I think it should not be handled a *leaked* memory.

You can check that adding a loop in your program (to dlopen/dlsym/dlclose
multiple times) do not increase the cache usage, as expected.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]