Should i do malloc() before using dlopen()?

Question

Below shown is the code snippet i am using. Should I allocate space using malloc before doing dlopen?

void* pvHandle = NULL;

/* Dynamically loading library */
pvHandle = dlopen ("libame.so", RTLD_LAZY | RTLD_GLOBAL);       
if (!pvHandle)
    {
        pszError = dlerror();
        cout << "Error : " << pszError;
    }

Please help me clear this doubt. Thanks in Advance.

What do you want to allocate specifically? I don't get your question. — πάντα ῥεῖ, Sep 08 '15 at 08:35
Which part of which documentation lead you to believe that you should allocate anything? — Kerrek SB, Sep 08 '15 at 08:38

score 3 · Accepted Answer · answered Sep 08 '15 at 08:35

3

No, dlopen returns an opaque handle to the library, you do not need to allocate any memory yourself.

answered Sep 08 '15 at 08:35

TartanLlama

63,752
13
157
193

So what will happen if i am not using dlclose() ? It shouldnt lead to any memory leak. rite? – A R Sep 08 '15 at 12:23
You could leak memory, file handles, whatever. You should call `dlclose`. – TartanLlama Sep 08 '15 at 12:27
dlclose() leading to segfault on exit. Please check this link : "http://stackoverflow.com/questions/6450828/segmentation-fault-when-using-dlclose-on-android-platform" . I am also facing same issue. As per this link it says we can avoid calling dlclose(). Any other suggestion appreciated. – A R Sep 08 '15 at 12:40
@user2599593 If you are encountering platform issues, you can probably get away with omitting the call, so long as you document the issue. – TartanLlama Sep 08 '15 at 12:44

Should i do malloc() before using dlopen()?

1 Answers1