Displaying 10 results from an estimated 10 matches for "dyld_print_initializers".
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 /sw/src/fink.build/llvm32-3.2-0/llvm-3.2/lib/Sup...
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)
> > llvm::sys::DynamicLibrary::getPermanentLibrary (filename=0x142903da8 "/sw/opt/llvm-3.2/lib/LLVMPolly.so", errMsg=0x7fff5fbfe6e0) at /sw/src/fink.build/llvm32-3....
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...
>>>
>>> (gdb)
>>> llvm::sys::DynamicLibrary::getPermanentLibrary (filename=0x142903da8 "/sw/opt/llvm-3.2/lib/LLVMPolly.so", errMsg=0x7fff5fbfe6e0) at /sw/src/fink.bui...
2012 Oct 22
0
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
...=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 made its way into the cc1 binary, probably it called some weak symbol which resolved in the main executable cc1.
>
> In gdb you can set:
> (gdb) set env DYLD_PRINT_INITIALIZERS
> and dyld will print out the address of each initializer before calling it. You can then run again and set a break point at that address and step through it.
>
> Also, the lazy bind info for LLVMPolly.so was a little odd in that all symbols were marked "flat-namespace". On...
2012 Oct 23
2
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
...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)...
2012 Oct 22
5
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
...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 made its way into the cc1 binary, probably it called some weak symbol which resolved in the main executable cc1.
In gdb you can set:
(gdb) set env DYLD_PRINT_INITIALIZERS
and dyld will print out the address of each initializer before calling it. You can then run again and set a break point at that address and step through it.
Also, the lazy bind info for LLVMPolly.so was a little odd in that all symbols were marked "flat-namespace". On MacOSX we norma...
2012 Oct 23
0
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
...the version of libcloog that was loaded when gcc (the main binary) was started
up, causing all kinds of mayhem on linux. Maybe this could cause the kind of
issue you are seeing, especially if the two libcloog library versions differ?
Ciao, Duncan.
>
> In gdb you can set:
> (gdb) set env DYLD_PRINT_INITIALIZERS
> and dyld will print out the address of each initializer before calling it. You can then run again and set a break point at that address and step through it.
>
> Also, the lazy bind info for LLVMPolly.so was a little odd in that all symbols were marked "flat-namespace". On Mac...
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 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 23
2
[LLVMdev] dyld: lazy symbol binding failed: fast lazy bind offset out of range
...ent 5 which is too large (4)
gcc-fsf-4.7: internal compiler error: Trace/BPT trap: 5 (program cc1)
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
>
>>
>> In gdb you can set:
>> (gdb) set env DYLD_PRINT_INITIALIZERS
>> and dyld will print out the address of each initializer before calling it. You can then run again and set a break point at that address and step through it.
>>
>> Also, the lazy bind info for LLVMPolly.so was a little odd in that all symbols were marked "flat-namespace&qu...