thr3ads.net - llvm dev - [LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range [Oct 2012]

If this information is useful, please help other people find it:
Share via:

Nick Kledzik

2012-Oct-22 18:40 UTC

[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
/sw/src/fink.build/llvm32-3.2-0/llvm-3.2/lib/Support/DynamicLibrary.cpp:77
> 77        void *handle = dlopen(filename, RTLD_LAZY|RTLD_GLOBAL);
> (gdb)
> Reading symbols for shared libraries ... done
> dyld: calling initializer function 0x100eea5b0 in
/sw/opt/llvm-3.2/lib/LLVMPolly.so
You need to set a break point at 0x100eea5b0 and run again until that break is
hit, then start stepping.
> Are there any tricks for identifying the order that the symbols are being
resolved?(gdb) set env DYLD_PRINT_BINDINGS 1
will show each use of a symbol as it is bound.  This can be *a lot* of
information.

-Nick

Jack Howarth

2012-Oct-22 18:52 UTC

head link

[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)
> > llvm::sys::DynamicLibrary::getPermanentLibrary (filename=0x142903da8
"/sw/opt/llvm-3.2/lib/LLVMPolly.so", errMsg=0x7fff5fbfe6e0) at
/sw/src/fink.build/llvm32-3.2-0/llvm-3.2/lib/Support/DynamicLibrary.cpp:77
> > 77        void *handle = dlopen(filename, RTLD_LAZY|RTLD_GLOBAL);
> > (gdb)
> > Reading symbols for shared libraries ... done
> > dyld: calling initializer function 0x100eea5b0 in
/sw/opt/llvm-3.2/lib/LLVMPolly.so
> 
> You need to set a break point at 0x100eea5b0 and run again until that break
is hit, then start stepping.
> 
> > Are there any tricks for identifying the order that the symbols are
being resolved?
> (gdb) set env DYLD_PRINT_BINDINGS 1
> will show each use of a symbol as it is bound.  This can be *a lot* of
information.
> 
> -Nick
Nick,
   I will try one other thing first. I'll rebuild gcc47 without graphite
support so cc1 has no linkages on cloog/ppl/isl
and the test it against a stock build of llvm32 to see if this suppresses the
error.
    Jack

Jack Howarth

2012-Oct-22 20:01 UTC

head link

[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)
> > llvm::sys::DynamicLibrary::getPermanentLibrary (filename=0x142903da8
"/sw/opt/llvm-3.2/lib/LLVMPolly.so", errMsg=0x7fff5fbfe6e0) at
/sw/src/fink.build/llvm32-3.2-0/llvm-3.2/lib/Support/DynamicLibrary.cpp:77
> > 77        void *handle = dlopen(filename, RTLD_LAZY|RTLD_GLOBAL);
> > (gdb)
> > Reading symbols for shared libraries ... done
> > dyld: calling initializer function 0x100eea5b0 in
/sw/opt/llvm-3.2/lib/LLVMPolly.so
> 
> You need to set a break point at 0x100eea5b0 and run again until that break
is hit, then start stepping.
> 
> > Are there any tricks for identifying the order that the symbols are
being resolved?
> (gdb) set env DYLD_PRINT_BINDINGS 1
> will show each use of a symbol as it is bound.  This can be *a lot* of
information.
> 
> -Nick
Nick,
    We can eliminate the linkages of ppl/isl/cloog in cc1 as the cause of the
problem. I rebuilt the gcc47 package with...

Configured with: ../gcc-4.7.2/configure --prefix=/sw --prefix=/sw/lib/gcc4.7
--mandir=/sw/share/man --infodir=/sw/lib/gcc4.7/info
--enable-languages=c,c++,fortran,lto,objc,obj-c++,java --with-gmp=/sw
--with-libiconv-prefix=/sw --without-ppl --without-cloog --with-mpc=/sw
--with-system-zlib --x-includes=/usr/X11R6/include --x-libraries=/usr/X11R6/lib
--program-suffix=-fsf-4.7

to disable the graphite support such that cc1 is linked as...

% otool -L  /sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1 
/sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1:
	/sw/lib/libintl.8.dylib (compatibility version 10.0.0, current version 10.1.0)
	/sw/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
	/sw/lib/libmpc.3.dylib (compatibility version 4.0.0, current version 4.0.0)
	/sw/lib/libmpfr.4.dylib (compatibility version 6.0.0, current version 6.1.0)
	/sw/lib/gmp5/libgmp.10.dylib (compatibility version 11.0.0, current version
11.5.0)
	/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
169.3.0)

Using a dragonegg.so plugin built against this compiler, still produces the
error...

dyld: lazy symbol binding failed: fast lazy bind offset out of range (53437,
max=2928) in image
/sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1
dyld: fast lazy bind offset out of range (53437, max=2928) in image
/sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1

when loading the /sw/opt/llvm-3.2/lib/LLVMPolly.so plugin. This is as much as I
can reduce
the cc1 linkages so I'll have to manually hunt for the symbol now. Sigh.
           Jack

Jack Howarth

2012-Oct-22 23:34 UTC

head link

[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)
> > llvm::sys::DynamicLibrary::getPermanentLibrary (filename=0x142903da8
"/sw/opt/llvm-3.2/lib/LLVMPolly.so", errMsg=0x7fff5fbfe6e0) at
/sw/src/fink.build/llvm32-3.2-0/llvm-3.2/lib/Support/DynamicLibrary.cpp:77
> > 77        void *handle = dlopen(filename, RTLD_LAZY|RTLD_GLOBAL);
> > (gdb)
> > Reading symbols for shared libraries ... done
> > dyld: calling initializer function 0x100eea5b0 in
/sw/opt/llvm-3.2/lib/LLVMPolly.so
> 
> You need to set a break point at 0x100eea5b0 and run again until that break
is hit, then start stepping.
> 
> > Are there any tricks for identifying the order that the symbols are
being resolved?
> (gdb) set env DYLD_PRINT_BINDINGS 1
> will show each use of a symbol as it is bound.  This can be *a lot* of
information.
> 
> -Nick
Nick,
   If I set 'break *0x100eea5b0', I didn't get any output from
DYLD_PRINT_BINDINGS being set.
However if I set the breakpoint at PluginLoader.cpp:29 which is near the loading
of LLVMPolly.so,
I get...

....
dyld: weak bind: LLVMPolly.so:0x100FB3130 = libc++.1.dylib:__ZdlPv, *0x100FB3130
= 0x7FFF898BD1AB
dyld: weak bind: LLVMPolly.so:0x100FB3138 = libc++.1.dylib:__Znam, *0x100FB3138
= 0x7FFF898BD173
dyld: weak bind: LLVMPolly.so:0x100FB3140 = libc++.1.dylib:__Znwm, *0x100FB3140
= 0x7FFF898BD0DF
dyld: calling initializer function 0x100ebb5b0 in
/sw/opt/llvm-3.2/lib/LLVMPolly.so
dyld: lazy symbol binding failed: fast lazy bind offset out of range (53437,
max=2928) in image
/sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1
dyld: fast lazy bind offset out of range (53437, max=2928) in image
/sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/c

The complete log is uploaded to http://llvm.org/bugs/attachment.cgi?id=9397 of
http://llvm.org/bugs/show_bug.cgi?id=14140.
I would also note the following...

1) cc1 doesn't appear to be linked against any libstdc++.

/sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1:
	/sw/lib/libintl.8.dylib (compatibility version 10.0.0, current version 10.1.0)
	/sw/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
	/sw/lib/libmpc.3.dylib (compatibility version 4.0.0, current version 4.0.0)
	/sw/lib/libmpfr.4.dylib (compatibility version 6.0.0, current version 6.1.0)
	/sw/lib/gmp5/libgmp.10.dylib (compatibility version 11.0.0, current version
11.5.0)
	/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
169.3.0)

whereas libPolly.so is always linked against the system libstdc++ shared
library...

/sw/opt/llvm-3.2/lib/LLVMPolly.so:
	/sw/lib/libisl.10.dylib (compatibility version 11.0.0, current version 11.0.0)
	/sw/lib/gmp5/libgmp.10.dylib (compatibility version 11.0.0, current version
11.5.0)
	/sw/lib/libcloog-isl.3.dylib (compatibility version 4.0.0, current version
4.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
169.3.0)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version
56.0.0)

2) The problem seems to be immune to which libstdc++ shared library that
/sw/lib/gcc4.7/lib/dragonegg.so
is linked against. I have built dragonegg both with the FSF gcc-fsf-4.7 compiler
to link in
the FSF libstdc++ as well with clang to use the system libstdc++. Both modes of
building LLVMPolly.so
produce the same fast lazy binding failure.

Any suggestions on where to go from here in debugging this?
          Jack

Jack Howarth

2012-Oct-23 19:50 UTC

head link

[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)
> > llvm::sys::DynamicLibrary::getPermanentLibrary (filename=0x142903da8
"/sw/opt/llvm-3.2/lib/LLVMPolly.so", errMsg=0x7fff5fbfe6e0) at
/sw/src/fink.build/llvm32-3.2-0/llvm-3.2/lib/Support/DynamicLibrary.cpp:77
> > 77        void *handle = dlopen(filename, RTLD_LAZY|RTLD_GLOBAL);
> > (gdb)
> > Reading symbols for shared libraries ... done
> > dyld: calling initializer function 0x100eea5b0 in
/sw/opt/llvm-3.2/lib/LLVMPolly.so
> 
> You need to set a break point at 0x100eea5b0 and run again until that break
is hit, then start stepping.
> 
> > Are there any tricks for identifying the order that the symbols are
being resolved?
> (gdb) set env DYLD_PRINT_BINDINGS 1
> will show each use of a symbol as it is bound.  This can be *a lot* of
information.
> 
> -Nick
Nick,
   Can you clarify what I should be looking for here? I assumed you expected
that I should see some symbol
bindings occur immediately after the initializer function in LLVMPolly.so is
called but before dyld throws
the "fast lazy bind offset out of range" error message. In the
http://llvm.org/bugs/attachment.cgi?id=9397,
the log file for a walk with DYLD_PRINT_INITIALIZERS and DYLD_PRINT_BINDINGS set
on darwin12, I only see...

(gdb) 
llvm::sys::DynamicLibrary::getPermanentLibrary (filename=0x141328518
"/sw/opt/llvm-3.2/lib/LLVMPolly.so", errMsg=0x7fff5fbfe6d0) at
/sw/src/fink.build/llvm32-3.2-0/llvm-3.2/lib/Support/DynamicLibrary.cpp:77
77        void *handle = dlopen(filename, RTLD_LAZY|RTLD_GLOBAL);
(gdb) 
Reading symbols for shared libraries ... done
dyld: bind: libisl.10.dylib:0x101292010 = libsystem_c.dylib:__DefaultRuneLocale,
*0x101292010 = 0x7FFF7A145890
dyld: bind: libisl.10.dylib:0x101292018 = libsystem_c.dylib:___stack_chk_guard,
*0x101292018 = 0x7FFF7A1474B0
....
dyld: weak bind: LLVMPolly.so:0x100FB3128 = libc++.1.dylib:__ZdaPv, *0x100FB3128
= 0x7FFF898BD1C6
dyld: weak bind: LLVMPolly.so:0x100FB3130 = libc++.1.dylib:__ZdlPv, *0x100FB3130
= 0x7FFF898BD1AB
dyld: weak bind: LLVMPolly.so:0x100FB3138 = libc++.1.dylib:__Znam, *0x100FB3138
= 0x7FFF898BD173
dyld: weak bind: LLVMPolly.so:0x100FB3140 = libc++.1.dylib:__Znwm, *0x100FB3140
= 0x7FFF898BD0DF
dyld: calling initializer function 0x100ebb5b0 in
/sw/opt/llvm-3.2/lib/LLVMPolly.so
dyld: lazy symbol binding failed: fast lazy bind offset out of range (53437,
max=2928) in image
/sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1
dyld: fast lazy bind offset out of range (53437, max=2928) in image
/sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1

Program received signal SIGTRAP, Trace/breakpoint trap.
0x00007fff5fc0109d in __dyld_dyld_fatal_error ()

where all of the bindings from LLVMPolly.so occur before the initializer
function is called. Was this behavior
expected?
   Also, as I noted on http://llvm.org/bugs/show_bug.cgi?id=14140#c13, a static
build of LLVMPolly.so on 10.6 exhibits the
same dyld error. Am I correct to assume that test proves that the offending
symbol can't be from libcloog-isl, libisl,
libgmp or libstdc++ because, when statically linked, those symbols can't be
obtained from cc1? Is it vaild to assume that the
offending symbol has to be both in the binding list seen when LLVMPolly.so loads
and the symbols (defined or undefined)
in cc1? Any suggestions on how to proceed in debugging this would be
appreciated.
         Jack

Nick Kledzik

2012-Oct-23 20:05 UTC

head link

[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...
>>> 
>>> (gdb)
>>> llvm::sys::DynamicLibrary::getPermanentLibrary
(filename=0x142903da8 "/sw/opt/llvm-3.2/lib/LLVMPolly.so",
errMsg=0x7fff5fbfe6e0) at
/sw/src/fink.build/llvm32-3.2-0/llvm-3.2/lib/Support/DynamicLibrary.cpp:77
>>> 77        void *handle = dlopen(filename, RTLD_LAZY|RTLD_GLOBAL);
>>> (gdb)
>>> Reading symbols for shared libraries ... done
>>> dyld: calling initializer function 0x100eea5b0 in
/sw/opt/llvm-3.2/lib/LLVMPolly.so
>> 
>> You need to set a break point at 0x100eea5b0 and run again until that
break is hit, then start stepping.
>> 
>>> Are there any tricks for identifying the order that the symbols are
being resolved?
>> (gdb) set env DYLD_PRINT_BINDINGS 1
>> will show each use of a symbol as it is bound.  This can be *a lot* of
information.
>> 
>> -Nick
> 
> Nick,
>   Can you clarify what I should be looking for here? I assumed you expected
that I should see some symbol
> bindings occur immediately after the initializer function in LLVMPolly.so
is called but before dyld throws
> the "fast lazy bind offset out of range" error message. In the
http://llvm.org/bugs/attachment.cgi?id=9397,
> the log file for a walk with DYLD_PRINT_INITIALIZERS and
DYLD_PRINT_BINDINGS set on darwin12, I only see...
> 
> (gdb) 
> llvm::sys::DynamicLibrary::getPermanentLibrary (filename=0x141328518
"/sw/opt/llvm-3.2/lib/LLVMPolly.so", errMsg=0x7fff5fbfe6d0) at
/sw/src/fink.build/llvm32-3.2-0/llvm-3.2/lib/Support/DynamicLibrary.cpp:77
> 77        void *handle = dlopen(filename, RTLD_LAZY|RTLD_GLOBAL);
> (gdb) 
> Reading symbols for shared libraries ... done
> dyld: bind: libisl.10.dylib:0x101292010 =
libsystem_c.dylib:__DefaultRuneLocale, *0x101292010 = 0x7FFF7A145890
> dyld: bind: libisl.10.dylib:0x101292018 =
libsystem_c.dylib:___stack_chk_guard, *0x101292018 = 0x7FFF7A1474B0
> ....
> dyld: weak bind: LLVMPolly.so:0x100FB3128 = libc++.1.dylib:__ZdaPv,
*0x100FB3128 = 0x7FFF898BD1C6
> dyld: weak bind: LLVMPolly.so:0x100FB3130 = libc++.1.dylib:__ZdlPv,
*0x100FB3130 = 0x7FFF898BD1AB
> dyld: weak bind: LLVMPolly.so:0x100FB3138 = libc++.1.dylib:__Znam,
*0x100FB3138 = 0x7FFF898BD173
> dyld: weak bind: LLVMPolly.so:0x100FB3140 = libc++.1.dylib:__Znwm,
*0x100FB3140 = 0x7FFF898BD0DF
> dyld: calling initializer function 0x100ebb5b0 in
/sw/opt/llvm-3.2/lib/LLVMPolly.so
> dyld: lazy symbol binding failed: fast lazy bind offset out of range
(53437, max=2928) in image
/sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1
> dyld: fast lazy bind offset out of range (53437, max=2928) in image
/sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1
> 
> Program received signal SIGTRAP, Trace/breakpoint trap.
> 0x00007fff5fc0109d in __dyld_dyld_fatal_error ()
> 
> where all of the bindings from LLVMPolly.so occur before the initializer
function is called. Was this behavior
> expected?
>   Also, as I noted on http://llvm.org/bugs/show_bug.cgi?id=14140#c13, a
static build of LLVMPolly.so on 10.6 exhibits the
> same dyld error. Am I correct to assume that test proves that the offending
symbol can't be from libcloog-isl, libisl,
> libgmp or libstdc++ because, when statically linked, those symbols
can't be obtained from cc1? Is it vaild to assume that the
> offending symbol has to be both in the binding list seen when LLVMPolly.so
loads and the symbols (defined or undefined)
> in cc1? Any suggestions on how to proceed in debugging this would be
appreciated.
As I said before, run once to get the address of the initializer being run
inside the dlopen call (0x100ebb5b0 in the case above).  Set a break point
there.  Run again.  When it stops at the break point (inside the initializer),
start stepping until it crashes.  You may need to step at the instruction level.

The point of the DYLD_PRINT_BINDINGS was so you can see what pointers dyld was
setting.  At some point in your trace you may be jumping through one of those
pointers.  You can check that the value makes sense and was not stomped by
something else.

-Nick

Maybe Matching Threads

Search for more apparently analagous threads

llvm dev - Oct 2012 - [LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range

[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range

[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range

[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range

[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range

[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range

[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range

Maybe Matching Threads