similar to: [LLVMdev] symbol not found (running passes by tools)

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

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

Hi everyone, I have a terrible feeling I'm doing something really silly here, but I can't seem to solve the problem after a day of trying now. I'm currently writing my own pass which I am running by loading it into the opt tool. Everything I had written in the pass so far had worked, until I started declaring an #include of some extra header files which I had written myself (they are

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

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) > >

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...

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

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 initially points to a helper which loads an index parameter specifying which function to

On Oct 23, 2012, at 1:57 PM, Jack Howarth wrote: > Nick, > Can I do this without access to a debug version of dyld? Using the copy of LLVMPolly.so with isl/cloog-isl/gmp statically linked, > I find that if I set the breakpoint to the address of the initializer... > > dyld: calling initializer function 0x100ebb3a0 in /sw/opt/llvm-3.2/lib/LLVMPolly.so > dyld: lazy symbol binding

Nick, While enhancing the fink llvm32 packaging to support the polly tool, I ran into a dyld failure when the dragonegg plugin tries to load LLVMPolly.so plugin... dyld: lazy symbol binding failed: fast lazy bind offset out of range (39257, max=7640) in image /sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin11.4.2/4.7.2/cc1 dyld: fast lazy bind offset out of range (39257, max=7640) in image

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

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

On Tue, Oct 23, 2012 at 09:41:46AM +0200, Duncan Sands wrote: > 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

I'm using the Ruby/FFI libvirt library and getting this consistently on Mac OS X: ruby-1.9.2-p0 > FFI::Libvirt.virInitialize dyld: lazy symbol binding failed: Symbol not found: _virThreadInitialize Referenced from: /usr/local/lib/libvirt.dylib Expected in: flat namespace dyld: Symbol not found: _virThreadInitialize Referenced from: /usr/local/lib/libvirt.dylib Expected in: flat

Hi When I do a "rake db:migrate", I get the following error: ---- (in /Users/sneigaard/work/rails/mailtimer) dyld: lazy symbol binding failed: Symbol not found: _mysql_init Referenced from: /Library/Ruby/Gems/1.8/gems/mysql-2.8.1/lib/ mysql_api.bundle Expected in: flat namespace dyld: Symbol not found: _mysql_init Referenced from: /Library/Ruby/Gems/1.8/gems/mysql-2.8.1/lib/

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

On Tue, Oct 23, 2012 at 02:03:15PM -0700, Nick Kledzik wrote: > > On Oct 23, 2012, at 1:57 PM, Jack Howarth wrote: > > Nick, > > Can I do this without access to a debug version of dyld? Using the copy of LLVMPolly.so with isl/cloog-isl/gmp statically linked, > > I find that if I set the breakpoint to the address of the initializer... > > > > dyld: calling

James Stanier wrote: > Hi everyone, > > I have a terrible feeling I'm doing something really silly here, but I can't > seem to solve the problem after a day of trying now. I'm currently writing > my own pass which I am running by loading it into the opt tool. Everything I > had written in the pass so far had worked, until I started declaring an > #include of some

On Oct 23, 2012, at 4:46 PM, Jack Howarth wrote: > On Tue, Oct 23, 2012 at 02:03:15PM -0700, Nick Kledzik wrote: >> >> On Oct 23, 2012, at 1:57 PM, Jack Howarth wrote: >>> Nick, >>> Can I do this without access to a debug version of dyld? Using the copy of LLVMPolly.so with isl/cloog-isl/gmp statically linked, >>> I find that if I set the breakpoint to

Hello LLVM devs, I’m running into the following problem when loading my custom passes in opt on OS X 10.9 (which work fine on Linux): dyld: lazy symbol binding failed: Symbol not found: __ZN4llvm9CalculateINS_8FunctionEPNS_10BasicBlockEEEvRNS_17DominatorTreeBaseINS_11GraphTraitsIT0_E8NodeTypeEEERT_ Referenced from: /Users/julian/Src/llvm/Debug+Asserts/lib/Nymblle.dylib Expected in: flat