similar to: [LLVMdev] Add RTLD_GLOBAL to dlopen

Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] Add RTLD_GLOBAL to dlopen"

2008 Jul 10
0
[LLVMdev] Add RTLD_GLOBAL to dlopen
On Wed, 9 Jul 2008, Bram Adams wrote: > Today, I've made the transition from LLVM 2.1 to 2.3. I invoke opt > with two dynamic libraries to "-load", the first of which contains > transformation passes and support code whereas the second one provides > extra passes which make use of the first library's support code. In > other words, the symbols loaded in for the
2012 Oct 23
1
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
On Mon, Oct 22, 2012 at 11:40:32AM -0700, Nick Kledzik wrote: > > On Oct 22, 2012, at 11:34 AM, Jack Howarth wrote: > > > Nick, > > I have uploaded the full walk with 'set env DYLD_PRINT_INITIALIZERS'. It didn't seem very informative > > as the dyld error occurs right after... > > > > (gdb) > >
2012 Oct 23
0
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
On Oct 23, 2012, at 12:50 PM, Jack Howarth wrote: > On Mon, Oct 22, 2012 at 11:40:32AM -0700, Nick Kledzik wrote: >> >> On Oct 22, 2012, at 11:34 AM, Jack Howarth wrote: >> >>> Nick, >>> I have uploaded the full walk with 'set env DYLD_PRINT_INITIALIZERS'. It didn't seem very informative >>> as the dyld error occurs right after...
2012 Oct 22
5
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
On Oct 22, 2012, at 11:34 AM, Jack Howarth wrote: > Nick, > I have uploaded the full walk with 'set env DYLD_PRINT_INITIALIZERS'. It didn't seem very informative > as the dyld error occurs right after... > > (gdb) > llvm::sys::DynamicLibrary::getPermanentLibrary (filename=0x142903da8 "/sw/opt/llvm-3.2/lib/LLVMPolly.so", errMsg=0x7fff5fbfe6e0) at
1998 May 27
3
dependencies in .so files
Thomas Lumley writes: > > > I've been trying to get Matt Calder's S compiler to work in R using R > COMPILE and R SHLIB so it will be fairly platform-independent. > > I'm sure someone has claimed in the past that it is possible/easy to > dyn.load() two dynamic libraries and have one call functions in the other. > I can't get it to work (Red Hat
2019 Dec 13
0
dlopen RTD_LAZY and RTLD_GLOBAL
All, I use a code which has a python (I use python36) wrapper loading shared libraries. The code worked fine in RHEL 7 but as I was testing it on Centos 8, python cannot import the shared library (the import is done via dlopen with flags set as > sys.setdlopenflags(os.RTLD_LAZY | os.RTLD_GLOBAL) python then does a bunch of imports and most results in a shared library with indefined
2012 Oct 22
0
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
On Mon, Oct 22, 2012 at 10:17:56AM -0700, Nick Kledzik wrote: > Jack, > > I looks like the code is calling dlopen() on LLVMPolly.so and it or something it links against has an initializer. The initialer is run before dlopen() returns and the crash is in the initializer. The message: > > dyld: fast lazy bind offset out of range (53437, max=7640) in image
2007 Apr 09
1
RTLD_GLOBAL flag for dlopen
I am just experimenting with a plugin loader and I found that there are problems with external symbols which are loaded at runtime. The solution is to add RTLD_GLOBAL to the dlopen mode, but I am not sure if this would cause other problems. Is this patch OK to go in? -------------- next part -------------- A non-text attachment was scrubbed... Name: rtld_global.diff Type: text/x-patch Size:
2012 Oct 22
0
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
On Mon, Oct 22, 2012 at 09:48:59AM -0400, Jack Howarth wrote: > On Sun, Oct 21, 2012 at 06:00:36PM -0700, Nick Kledzik wrote: > > Jack, > > > > Some binary has an initializer which dyld is calling. Somehow the initializer gets to: > > #4 0x0000000100f3b2c0 in Json::Value::maxUInt () > > which is calling a function in another dylib for the first time. When you
2012 Oct 23
2
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
On Tue, Oct 23, 2012 at 01:05:04PM -0700, Nick Kledzik wrote: > On Oct 23, 2012, at 12:50 PM, Jack Howarth wrote: > > On Mon, Oct 22, 2012 at 11:40:32AM -0700, Nick Kledzik wrote: > >> > >> On Oct 22, 2012, at 11:34 AM, Jack Howarth wrote: > >> > >>> Nick, > >>> I have uploaded the full walk with 'set env
2008 Mar 12
1
[LLVMdev] [PATCH] Get dlerror() messages
Hello, Attached is a simple fix for getting error messages from dlerror in LoadLibraryPermanently. The current code modifies the value of a pointer that is passed by value, so the caller never gets the message. Hope this helps, Julien -- Julien Lerouge PGP Key Id: 0xB1964A62 PGP Fingerprint: 392D 4BAD DB8B CE7F 4E5F FA3C 62DB 4AA7 B196 4A62 PGP Public Key from: keyserver.pgp.com --------------
2012 Oct 23
0
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
Hi, > I looks like the code is calling dlopen() on LLVMPolly.so and it or something it links against has an initializer. The initialer is run before dlopen() returns and the crash is in the initializer. The message: > > dyld: fast lazy bind offset out of range (53437, max=7640) in image /sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1 > > means the initializer
2012 Oct 22
2
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
On Sun, Oct 21, 2012 at 06:00:36PM -0700, Nick Kledzik wrote: > Jack, > > Some binary has an initializer which dyld is calling. Somehow the initializer gets to: > #4 0x0000000100f3b2c0 in Json::Value::maxUInt () > which is calling a function in another dylib for the first time. When you call a function in another dylib, you actually jump through a (lazy) pointer. The pointer
2012 Oct 22
5
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
Jack, I looks like the code is calling dlopen() on LLVMPolly.so and it or something it links against has an initializer. The initialer is run before dlopen() returns and the crash is in the initializer. The message: dyld: fast lazy bind offset out of range (53437, max=7640) in image /sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1 means the initializer called something which
2003 Oct 25
3
[LLVMdev] version 1.0, compiling under cygwin
Hello llvmdev, (just for fun) I've tried to compile LLVM under cygwin. With "make -k" I got only: ----------------- DynamicLinker.cpp: In function `void* GetAddressOfSymbol(const char*)': DynamicLinker.cpp:40: error: `RTLD_DEFAULT' undeclared (first use this function) DynamicLinker.cpp:40: error: (Each undeclared identifier is reported only once for each
2006 Aug 20
3
[LLVMdev] Weird behavior of llvm-ld
Hi, Op 20-aug-06, om 21:18 heeft Reid Spencer het volgende geschreven: > I looked over your patch and it looks good. I applied a patch based on > yours. The llvm-ld tool now uses the PluginLoader just like the opt > tool. It will also run some cleanup passes after the loaded plugins > run > to ensure cruft is removed. OK, thanks. Your patch seems to work, although I also get
2006 Aug 16
2
[LLVMdev] Weird behavior of llvm-ld
Hi, I'm using LLVM 1.8 with the GCC4-frontend on a Slackware 10.2 box (GCC 3.3.6). When issuing the following command (line 14 in a script called manual.sh): llvm-ld -O1 *.trans -L${SOME_LIB_DIR} -L${SOME_OTHER_LIB_DIR} -L${LLVM_FRONT}/lib -lSOME_LIB -lSOME_OTHER_LIB -load=${MY_LIB_DIR}/opt1.so -load=${MY_LIB_DIR}/opt2.so -debug-pass=Details -debug -o test ... I get the following
2006 Nov 15
3
[LLVMdev] 1.9 Prerelease Available for Testing
> When building LLVM 1.9 on OSX 10.4.8, I get (after a while, see attachment): > > make[1]: *** No rule to make target `/path/to/llvm-build/Debug/bin/tblgen', > needed by `/path/to/llvm-build/lib/VMCore/Debug/Intrinsics.gen.tmp'. Stop. > make: *** [install] Error 1 > > when doing: > > $LLVM_SRC/configure --prefix=$LLVM_INSTALL --with-llvmgccdir=$LLVM_FRONT
2013 Oct 06
1
[LLVMdev] how to runtime link to shared library symbols in the JIT?
I would like to load shared libraries at runtime for use in some JIT'd code. I can't find much about how the JIT resolves symbols, so can somebody answer a few questions for me? 1. Will the symbols from a dlopen'd library with RTLD_GLOBAL be available? In this case I can manually dlopen the libraries prior to the JIT run. 2. Can I derive from ExecutionEngine and override the
2006 Nov 15
4
[LLVMdev] 1.9 Prerelease Available for Testing
Hi, There is a typo in $LLVM_SRC/Makefile.rules on line 750 where it says : SharedLibKindMessage := "Lodable Module" instead of SharedLibKindMessage := "Loadable Module" Op 15-nov-06, om 15:54 heeft Bram Adams het volgende geschreven: > Didn't check > LLVM's test suite. Doing the simple LLVM-tests (on Slackware 10.2) gets: === Summary ===