shared-libraries

I am migrating a production app from bamboo stack to cedar, I successfully pushed the app on cedar but resulting in error like LoadError: Could not open library 'lib.so': lib.so: cannot open shared object file: No such file or directory from /app/vendor/bundle/ruby/1.9.1/gems/ffi-1.0.9/lib/ffi/library.rb:75:in `block in ffi_lib' from /app/vendor/bundle/ruby/1.9.1/gems/ffi-1.0.9/lib/ffi/library.rb:54:in `map' from /app/vendor/bundle/ruby/1.9.1/gems/ffi-1.0.9/lib/ffi/library.rb:54:in `ffi_lib' 0.1.3/lib/tidy_ffi/interface.rb:5:in `' Looks like some native libs are missing on Cedar stack which

Assume I have binary library (*.so) and a binary program using that library (i.e. I do not own the source code for either). How can I find out which of the library's functions are called at run time. I would like to know their names, but do not need live info. Neither of the binaries includes debugging symbols. The objdump command dumps external symbol references from a binary. The typical use case involves running it with the -T option, to dump a binary's external symbol references. For example, running objdump -T on /bin/ls : /bin/ls: file format elf64-x86-64 DYNAMIC SYMBOL TABLE:

I want to write a shared library in such a way that it is possible to isolate it’s memory usage from the application it is linked against. That is, if the shared library, let’s call it libmemory.so , calls malloc , I want to maintain that memory in a separate heap from the heap that is used to service calls to malloc made in the application. This question isn't about writing memory allocators, it more about linking and loading the library and application together. So far I’ve been experimenting with combinations of function interposition, symbol visibility, and linking tricks. So far, I can’t

I am relatively new to Linux development, having been using Windows for a while now. Anyway, I am compiling a C++ game using g++ on both Windows and Linux (using mingw32 when needed), and am linking against SDL2 and SDL2_mixer. On Windows, one would only need to put the DLL files in the same folder as the executable and everything would run fine. On Linux however, although the code compiled just fine with not even a single warning, I get this at runtime : ./nKaruga: error while loading shared libraries: libSDL2_mixer-2.0.so.0: cannot open shared object file: No such file or directory although

Based on some SO questions -- and some further reference found --, I'm trying to build a makefile able to: find, given the directories in $(SRC) , the .cpp files to be compiled; compile the .cpp , producing .o objects; generate .so shared objects from each .o formerly compiled. What the make file is supposed to do to achieve that is: find, given the directories in $(SRC) , the .cpp files to be compiled; build the dependency list for each .cpp using -MM compiler's flag; annotate/add each dependency using $(eval ...) ; evaluate/solve each dependency found, producing both the .o and .so files.

I've got a shared object, which I'll call 'libFoo.so', compiled against the NDK. I have a java project (I'll call it 'jarlib') that makes use of that shared object, by calling System.loadLibrary("Foo"); That java project, I export as a jar, and use in an android application. If I comment out all the bits about the shared object, the jar works fine, and I'm able to interact with it perfectly. I can use jarlib, along with the shared object from a Unity android application with the shared object in ./lib/armeabi/libFoo.so, and it loads it up all peachy. I'm trying to use the jarlib and libFoo.so

I stumbled about an issue while using libstdc++'s std::any implementation with mingw across a shared library boundary. It produces a std::bad_any_cast where it obviously should not (i believe). I use mingw-w64, gcc-7 and compile the code with -std=c++1z. The simplified code: main.cpp: #include <any> #include <string> // prototype from lib.cpp void do_stuff_with_any(const std::any& obj); int main() { do_stuff_with_any(std::string{"Hello World"}); } lib.cpp: Will be compiled into a shared library and linked with the executable from main.cpp. #include <any> #include <iostream> void do_stuff_with

Can any one of you help me in converting an windows dll file in a .so file. You might try re-compiling the source code to the dll to a shared object. This may help you get started, after ensuring the code is indeed portable. Edit: Here is yet another link that can help guide you through the process of creating a shared library using GCC and other parts of the GNU tool chain. This link will help you to discover pitfalls that other people had when undertaking a project similar to this. There is only so much help that can be provided for such a specific task, especially with so many unknowns. If