Quote:
Originally Posted by
migurus
just a side note: why not to use shared memory (shmop,shmctl,shmget)?
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 my application.
====================================================================
To wrap this thread up, I just want to thank you, Corona688, for your advice.
Although they didn't help me as much as I hoped, you definitely gave me some new things to feed the brain
Now hold on to you shorts, here comes the solution for my problem
As I said on my first post, on CentOS 32bit release everything was ok, but on 64bit, I got garbage addresses when performing dlsym, hence I assumed it was some kind of compiler issue. After compiling my shared objects with a lot of possible combinations of options for gcc and failing, I got the most retarded idea ever : I just moved util_load_library to another C+h file, and it worked without any complains. The C file where I moved it is one of the files from where I call my loader function.
I assume this had something to do with the fact that the initial C+h file could have been packed in some other so, and maybe this messed up the address space on the 64bit version.
Anyway, just wanted to let you know I solved my issue in the weirdest way possible
Thanks a lot for you support!