search for: dyld_stub_bind

...shows... > > (gdb) bt > #0 0x00007fff5fc0123f in __dyld__ZN13dyldbootstrap5startEPK12macho_headeriPPKclS2_Pm () > #1 0x00007fff5fc02138 in __dyld__ZN4dyld4haltEPKc () > #2 0x00007fff5fc04048 in __dyld__ZN4dyld18fastBindLazySymbolEPP11ImageLoaderm () > #3 0x00007fff8bd808ee in dyld_stub_binder_ () > #4 0x0000000100faf3e0 in Json::Value::maxUInt () > #5 0x0000000100ebad65 in pch_address_space () > #6 0x0000000100ebb5a0 in pch_address_space () > #7 0x0000000100ebb5b9 in pch_address_space () > #8 0x00007fff5fc13378 in __dyld__ZN16ImageLoaderMachO18doModInitFunctionsERK...

...ce from the final crash point shows... (gdb) bt #0 0x00007fff5fc0123f in __dyld__ZN13dyldbootstrap5startEPK12macho_headeriPPKclS2_Pm () #1 0x00007fff5fc02138 in __dyld__ZN4dyld4haltEPKc () #2 0x00007fff5fc04048 in __dyld__ZN4dyld18fastBindLazySymbolEPP11ImageLoaderm () #3 0x00007fff8bd808ee in dyld_stub_binder_ () #4 0x0000000100faf3e0 in Json::Value::maxUInt () #5 0x0000000100ebad65 in pch_address_space () #6 0x0000000100ebb5a0 in pch_address_space () #7 0x0000000100ebb5b9 in pch_address_space () #8 0x00007fff5fc13378 in __dyld__ZN16ImageLoaderMachO18doModInitFunctionsERKN11ImageLoader11LinkConte...

...ss despite that I am running on MacOS. (I’ve not tried windows yet.) I seem to be able to compile with clang a proper mach object file for a hello function. However, when I link this function into a shared library I (surprisingly for a shared lib?) get undefined symbols like _printf, stub runtime: dyld_stub_binder, _main, etc. Using the flag -undefined dynamic_lookup I get no errors or warnings but then when I try to link the shared library to a main program I get the error: ld: malformed dylib has MH_NO_REEXPORTED_DYLIBS flag but no LC_REEXPORT_DYLIB load commands: ./libhello.dylib file './lib...

...on MacOS. (I’ve not > tried windows yet.) > > I seem to be able to compile with clang a proper mach object file for a > hello function. However, when I link this function into a shared library I > (surprisingly for a shared lib?) get undefined symbols like _printf, stub > runtime: dyld_stub_binder, _main, etc. Using the flag > > -undefined dynamic_lookup > > I get no errors or warnings but then when I try to link the shared library > to a main program I get the error: > > ld: malformed dylib has MH_NO_REEXPORTED_DYLIBS flag > but no LC_REEXPORT_DYLIB load commands:...

+glider The compiler hardly matters here, I would expect the same failures with clang. Alex, could you please take a look? --kcc On Thu, Nov 29, 2012 at 9:55 PM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > Nick, > Can you take a quick look at the asan_eh_bug.tar.bz testcase > I uploaded into the newly opened radr://12777299, "potential > pthread/eh bug exposed

Nick, Can you take a quick look at the asan_eh_bug.tar.bz testcase I uploaded into the newly opened radr://12777299, "potential pthread/eh bug exposed by libsanitizer". The FSF gcc developers have ported llvm.org's asan code into FSF gcc (and are keeping it synced to the upstream llvm.org code). I have been helping with the darwin build and testing -fsanitize=address against the

...that I am running on MacOS. (I’ve not tried windows yet.) > > I seem to be able to compile with clang a proper mach object file for a hello function. However, when I link this function into a shared library I (surprisingly for a shared lib?) get undefined symbols like _printf, stub runtime: dyld_stub_binder, _main, etc. Using the flag > > -undefined dynamic_lookup > > I get no errors or warnings but then when I try to link the shared library to a main program I get the error: > > ld: malformed dylib has MH_NO_REEXPORTED_DYLIBS flag > but no LC_REEXPORT_DYLIB load command...

...> tried windows yet.) >> >> I seem to be able to compile with clang a proper mach object file for a >> hello function. However, when I link this function into a shared library I >> (surprisingly for a shared lib?) get undefined symbols like _printf, stub >> runtime: dyld_stub_binder, _main, etc. Using the flag >> >> -undefined dynamic_lookup >> >> I get no errors or warnings but then when I try to link the shared >> library to a main program I get the error: >> >> ld: malformed dylib has MH_NO_REEXPORTED_DYLIBS flag >> but no L...

...am running on MacOS. (I’ve not tried windows yet.) >> >> I seem to be able to compile with clang a proper mach object file for a hello function. However, when I link this function into a shared library I (surprisingly for a shared lib?) get undefined symbols like _printf, stub runtime: dyld_stub_binder, _main, etc. Using the flag >> >> -undefined dynamic_lookup >> >> I get no errors or warnings but then when I try to link the shared library to a main program I get the error: >> >> ld: malformed dylib has MH_NO_REEXPORTED_DYLIBS flag >> but no LC...

...t;> I seem to be able to compile with clang a proper mach object file for >>>>> a hello function. However, when I link this function into a shared library >>>>> I (surprisingly for a shared lib?) get undefined symbols like _printf, stub >>>>> runtime: dyld_stub_binder, _main, etc. Using the flag >>>>> >>>>> -undefined dynamic_lookup >>>>> >>>>> I get no errors or warnings but then when I try to link the shared >>>>> library to a main program I get the error: >>>>> >&gt...