search for: sharedlibrary

Displaying 9 results from an estimated 9 matches for "sharedlibrary".

Did you mean: shared_library
2018 Apr 16
2
lldb stops on every call to dlopen
...If I continue, it will load a few more then halt again, which makes debugging from startup impractical since there are so many libraries to be loaded (more than a hundred of them). When I build and debug this same C++ on macOS, the debugger works fine. I have verified that target.process.stop-on-sharedlibrary-events is false. I turned on dyld logging and I see lots of log messages about RendezvousBreakpoint being hit, but I don’t see anything that sheds light on why some libraries load without stopping but others don’t. I have tried to recreate this in a trivial program that calls dlopen in a loop, but...
2018 Apr 17
0
lldb stops on every call to dlopen
...t. The fact that you see the rendezvous breakpoint being hit many times is not surprising. We get those every time the library is loaded (we need that to load relevant debug info and set potential breakpoints). However, they should generally not be surfaced to the user (unless you have the stop-on-sharedlibrary-events setting set, which you don't). The part that is suspicious to me is that __restore_rt shows up on the top of the backtrace. This is a trampoline used to return from signal handlers, and it would seem to indicate that you got some sort of a signal while loading the libraries. I don't...
2018 Apr 17
1
[lldb-dev] lldb stops on every call to dlopen
...u see the rendezvous breakpoint being hit many times is not > surprising. We get those every time the library is loaded (we need that to > load relevant debug info and set potential breakpoints). However, they > should generally not be surfaced to the user (unless you have the > stop-on-sharedlibrary-events setting set, which you don't). > > The part that is suspicious to me is that __restore_rt shows up on the top > of the backtrace. This is a trampoline used to return from signal handlers, > and it would seem to indicate that you got some sort of a signal while > loading t...
2013 Nov 19
2
[LLVMdev] [lld] process undefined atoms from shared library only once
...rt-group/--end-group contains archive files. If they contain dynamic libraries, the undefined atoms from the dynamic libraries are processed whenever the group is iterated again. I am trying to find out a way to make the resolver add undefined atoms from the shared library only *once*, when the SharedLibrary is first visited as part of the Group. The only approach that I can think of is having a std::map in the resolver and using that to process undefined atoms from shared libraries the first time the shared library is visited. I dont like this approach as its not clean. Any alternative approache...
2013 Nov 19
0
[LLVMdev] [lld] process undefined atoms from shared library only once
...ins archive files. > > If they contain dynamic libraries, the undefined atoms from the dynamic > libraries are processed whenever the group is iterated again. > > I am trying to find out a way to make the resolver add undefined atoms > from the shared library only *once*, when the SharedLibrary is first > visited as part of the Group. > > The only approach that I can think of is having a std::map in the resolver > and using that to process undefined atoms from shared libraries the first > time the shared library is visited. I dont like this approach as its not > clean. &...
2012 Jul 18
3
[LLVMdev] [lld] Atom object model refactoring.
...e current atom object model that I would like to fix. The current 4 atoms are not expressive enough. We need to be able to serialize a larger set of atoms, many of which are format specific. The set of common atoms (shared between all formats) should be the set that the resolver requires to work. SharedLibrary is not included in this (by looking at the source code). The driving use case for this for me is the Import Address Table in PE/COFF. It is a section created by the writer that specifies external symbols to import and then acts as the GOT/PLT at runtime. Building this table requires extra informat...
2013 Jul 18
2
Help building OPUS library using FIXED_POINT option
...FIX.c [exec] Compile x86 : 1 <= warped_autocorrelation_FIX.c [exec] StaticLibrary : lib0.a [exec] StaticLibrary : lib1.a [exec] StaticLibrary : lib0.a [exec] StaticLibrary : lib1.a [exec] StaticLibrary : lib0.a [exec] StaticLibrary : lib1.a [exec] SharedLibrary : libdmt_opus.so [exec] SharedLibrary : libdmt_opus.so [exec] SharedLibrary : libdmt_opus.so [exec] C:/android/android-ndk-r8e/toolchains/arm-linux-androideabi-4.6/preb uilt/windows/bin/../lib/gcc/arm-linux-androideabi/4.6/../../../../arm-linux-andr oideabi/bin/ld.exe: ./obj/local...
2013 Nov 19
1
[LLVMdev] [lld] process undefined atoms from shared library only once
...gt; >> If they contain dynamic libraries, the undefined atoms from the dynamic >> libraries are processed whenever the group is iterated again. >> >> I am trying to find out a way to make the resolver add undefined atoms >> from the shared library only *once*, when the SharedLibrary is first >> visited as part of the Group. >> >> The only approach that I can think of is having a std::map in the resolver >> and using that to process undefined atoms from shared libraries the first >> time the shared library is visited. I dont like this approach as i...
2012 Jul 18
0
[LLVMdev] [lld] Atom object model refactoring.
...t; The current 4 atoms are not expressive enough. We need to be able to >>> serialize a larger set of atoms, many of which are format specific. >>> >>> The set of common atoms (shared between all formats) should be the set >>> that the resolver requires to work. SharedLibrary is not included in >>> this (by looking at the source code). >>> >>> The driving use case for this for me is the Import Address Table in >>> PE/COFF. It is a section created by the writer that specifies external >>> symbols to import and then acts as th...