shared-libraries

问题 i'm using gdb 7.2 on ubuntu 10.10 while stepping with step i get to a point that looks (literally) like this: 0x00130a2c in boost::contexts::context::impl_t::impl_t(void (*)(void*), void*, unsigned int, boost::contexts::context::impl_t*, std::auto_ptr<boost::contexts::context::allocator_base>) () from /home/lurscher/third_party/boost_1_45_0/stage/lib/libboost_context.so.1.45.0 So i want now to associate the appropiate source files; which likely should be on /home/lurscher/third_party/boost_1

问题 I'm porting a big chunk of native code with several interdependent libraries. Loading the code fails since Android linker only looks dependencies in /system/lib/ and not in the application install directory at /data/data/com.packagename.nnn/lib . As a first workaround I loaded all .so's from Java with System.load() in correct dependency order . This solution isn't satisfactory for me mostly because the set of libraries changes from build to build due to plugin architecture. Also the UI

问题 I think this question is rather easy for you shell scripting monsters. I am looking for the most elegant and shortest way to create symbolic links to shared libraries for Unix by means of a bash shell script. What I need is starting out with a list of shared library files such as "libmythings.so.1.1, libotherthings.so.5.11", get the symbolic links created such as: libmythings.so -> libmythings.so.1 -> libmythings.so.1.1 libotherthings.so -> libotherthings.so.5 -> libotherthings.so.5.11 The

问题 I'm building a shared library with f-no-rtti . Internally, this library throws std:invalid_argument and catches std::exception , but the catch clause is never entered. The following code reproduces the problem (g++ 4.2, Mac OS X 10.6): // library.cpp: exports f(), compiled with -fno-rtti #include <stdexcept> #include <iostream> extern "C" { void f() { try { throw std::invalid_argument("std::exception handler"); } catch( std::exception& e) { std::cout << e.what() << "\n"; } catch(...) { std:

问题 Sam Newman states in his book Building Microservices The evils of too much coupling between services are far worse than the problems caused by code duplication I just don't understand how the shared code between the services is evil. Does the author mean the service boundaries themselves are poorly designed if a need for a shared library emerges, or does he really mean I should duplicate the code in the case of common business logic dependency? I don't see what that solves. Let's say I have a

问题 The packages I'm toying with here are rather unknown, but nevertheless the problem is rather generic. Basically, I'm trying to compile Python module (called rql) with C++ extension. The extension uses external framework called gecode, which contains several libraries. I compiled gecode and installed locally. Now, let the output speak for itself: red@devel:~/build/rql-0.23.3$ echo $LD_LIBRARY_PATH /home/red/usr/lib red@devel:~/build/rql-0.23.3$ ls $LD_LIBRARY_PATH | grep libgecodeint

问题 I am a bit confused about how to install R (via compilation) as a shared library. The instructions here (Rpy2) say that I should do the following: # <go to the R source directory> make distclean ./configure --enable-R-shlib make make install but the first make ( make distclean ) would remove any previous installation of R under the same directory tree (e.g. the contents of the bin folder). What if I want to use the same installation for the R interpreter and the shared libraries? For example,

问题 I need to use an alternate glibc version, newer than the one installed on my system ( 2.18 vs 2.15 ). Several related issues are covered here and here. The specific question I'm asking here is the following: I set up the library path of the new dynamic linker ( ld-2.18.so ) so that the new libc ( libc-2.18.so ) is found ahead of the old libc ( libc-2.15.so ). However, when I try to run a program with the new ld , the old version of libc is picked up, generating a SEGV . Why is that happening?

问题 I have created one OSGi plugin (Bundle) using eclipse File-->New-->Other-->Plug-in Project called plugin 1. I want to use a native .so library in this plugin. I have added libtest_app_wrap1.so at the root of my plugin project. my project structure looks like below And here is the manifest file Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: JniTest Bundle-SymbolicName: JniTest Bundle-Version: 1.0.0.qualifier Bundle-Activator: jnitest.Activator Bundle-RequiredExecutionEnvironment:

问题 I've recently begun working in an enterprise software environment with hundreds of different applications all confined to their own "silos." One of my tasks is to try to standardize things a bit, and the first attempt will be a standard event logging. Currently, the company's "standard" is "everyone should use Enterprise Library for logging." What this translates to in reality is that different developers working on different projects implement different logging in different ways, and just