Search Results

dlfcn.h was included in each case in the C file containing the function body.
That was not the issue.
If there was a problem with the headers, I assume the 32bit version wouldn't have worked either.

Because I pack a large number of data arrays in the shared object, and I would need to do more work to also implement some kind of memory map on that.
Besides, my shared objects will be patches to...

Well, it is declared in util.h as
int util_load_library (const char *lib_file, void **handle);

Then the function code from the previous post is placed inside util.c, which includes util.h.
...

Thank you for that remark.

However, the reason why my stuff works on CentOS 32bit, and not on CentOS 64bit is way beyond my comprehension.

The code for loading the so and accessing the data...

perror or dlerror ?
I tried dlerror so far, but nothing interesting there :) Didn't think about perror yet, I'll give it a try

EDIT:
Is there anything wrong with the way I build my .so file ?...

Thanks, but we've already looked into this, and it would give us a lot of trouble in case we need debugging, or changing the ridiculous amount of arrays in the shared object.

right now I am...

I already used -fPIC when making the .o object.
I'll redeploy my app on 64bit architecture and add the -fPIC option to the second call to gcc, and let you know how that went.

Hello,

I am not that experienced with Linux, and I am currently facing some issues.

The application I'm working on uses hundreds of threads. To optimize the memory usage, I am putting all my...