search for: dladdr

...ostream&)': /src/Compilers/llvmHead/llvm/lib/Support/Unix/Signals.inc:418:5: error: 'Dl_info' was not declared in this scope Dl_info dlinfo; ^ /src/Compilers/llvmHead/llvm/lib/Support/Unix/Signals.inc:419:28: error: 'dlinfo' was not declared in this scope dladdr(StackTrace[i], &dlinfo); ^ /src/Compilers/llvmHead/llvm/lib/Support/Unix/Signals.inc:419:34: error: 'dladdr' was not declared in this scope dladdr(StackTrace[i], &dlinfo); ^ /src/Compilers/llvmHead/llvm/lib/Supp...

Googling indicates that cygwin doesn't have that functionality. Or, at least, didn't in 2010, when someone asked about the same problem: https://cygwin.com/ml/cygwin/2010-01/msg00596.html "cygwin has only dlsym() not the SGI DL_info + dladdr() yet. clang just needs it to get the path for the CIndex dll. This should be possible with the code in the LLVM_ON_WIN32 section, and convert then the path from win to posix with cygwin_conv_path()." On Thu, Jun 30, 2016 at 11:16 AM, Martin J. O'Riordan via llvm-dev < llvm-dev at li...

hi, my old code compiles well on 3.1, but fails on 3.2. the compile error is like below. ... g++ -o vc main.o `llvm-config --libs all --ldflags` /usr/lib/libLLVMSupport.a(Signals.o): In function `PrintStackTrace(void*)': Signals.cpp:(.text+0x6c8): undefined reference to `dladdr' Signals.cpp:(.text+0x749): undefined reference to `dladdr' collect2: error: ld returned 1 exit status make: *** [vc] Error 1 this is on Ubuntu 12.4, 64-bit. any idea on how to fix this? thanks. Jun -------------- next part -------------- An HTML attachment was scrubbed... URL: <http:...

ISSUE: In Interpreter::getCurrentExecutablePath(), dladdr() is a Solarisism. Luckily, getCurrentExecutablePath isn't being currently used anywhere in lli. ACTION: Wrap the method contents with #ifdef __sun__ ... #else return ""; #endif. If this functionality is actually desired, it would be more portable to hack up main() to join getc...

...r*, void*)': >> Unix/Path.inc:365: error: 'Dl_info' was not declared in this scope >> Unix/Path.inc:365: error: expected `;' before 'DLInfo' >> Unix/Path.inc:366: error: 'DLInfo' was not declared in this scope >> Unix/Path.inc:366: error: 'dladdr' was not declared in this scope >> gmake[1]: *** >> [/home/home/ac/psimmons/llvm/llvm-2.7/lib/System/Release/Path.o] Error 1 >> gmake[1]: Leaving directory >> `/home/home/ac/psimmons/llvm/llvm-2.7/lib/System' >> gmake: *** [all] Error 1 >> -bash-3.2$ pw...

...code compiles well on 3.1, but fails on 3.2. > the compile error is like below. > > > ... > g++ -o vc main.o `llvm-config --libs all --ldflags` > /usr/lib/libLLVMSupport.a(Signals.o): In function `PrintStackTrace(void*)': > Signals.cpp:(.text+0x6c8): undefined reference to `dladdr' > Signals.cpp:(.text+0x749): undefined reference to `dladdr' > collect2: error: ld returned 1 exit status > make: *** [vc] Error 1 > > > this is on Ubuntu 12.4, 64-bit. any idea on how to fix this? Adding -ldl explicitly might help. Dmitri -- main(i,j){for(i=2;;i++){f...

...at would also fix the chroot problem. > > > > This is not a chroot problem. As shown above, I do not get a valid > clang path > > to manipulate and discover include directories, etc. > > > > The other method in lib/Support/Unix/Path.inc (i.e. dladdr, > realpath) works. > > > > I still maintain that I need the configure option. > > Sorry for being mean, but this is a workaround for a bug in the > linux kernel that was > fixed years ago and is only visible when using an obscure revision >...

...s::Path::GetMainExecutable(const char*, void*)': Unix/Path.inc:365: error: 'Dl_info' was not declared in this scope Unix/Path.inc:365: error: expected `;' before 'DLInfo' Unix/Path.inc:366: error: 'DLInfo' was not declared in this scope Unix/Path.inc:366: error: 'dladdr' was not declared in this scope gmake[1]: *** [/home/home/ac/psimmons/llvm/llvm-2.7/lib/System/Release/Path.o] Error 1 gmake[1]: Leaving directory `/home/home/ac/psimmons/llvm/llvm-2.7/lib/System' gmake: *** [all] Error 1 -bash-3.2$ pwd Is this a known problem? How should I go about fix...

...t;> your fallback? That would also fix the chroot problem. > > > > This is not a chroot problem. As shown above, I do not get a valid clang > path > > to manipulate and discover include directories, etc. > > > > The other method in lib/Support/Unix/Path.inc (i.e. dladdr, realpath) > works. > > > > I still maintain that I need the configure option. > > Sorry for being mean, but this is a workaround for a bug in the linux > kernel that was > fixed years ago and is only visible when using an obscure revision control > system. > > A...

...utable(const char*, void*)': > Unix/Path.inc:365: error: 'Dl_info' was not declared in this scope > Unix/Path.inc:365: error: expected `;' before 'DLInfo' > Unix/Path.inc:366: error: 'DLInfo' was not declared in this scope > Unix/Path.inc:366: error: 'dladdr' was not declared in this scope > gmake[1]: *** > [/home/home/ac/psimmons/llvm/llvm-2.7/lib/System/Release/Path.o] Error 1 > gmake[1]: Leaving directory > `/home/home/ac/psimmons/llvm/llvm-2.7/lib/System' > gmake: *** [all] Error 1 > -bash-3.2$ pwd > > Is this a k...

I tried to Build LLVM under Syllable, but it was failed on the next moment http://clip2net.com/clip/m0/1246547164-clip-99kb.png any ideas? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090702/346df366/attachment.html>

...rough the list of call frames and calls a callback for each one. Within the callback, I can get the value of the return address for each call frame using _Unwind_GetIP(). So far so good. The problem is converting those addresses into meaningful symbols. For some reason that I don't understand, dladdr() doesn't seem to work on LLVM-generated functions, even though I know those functions have full DWARF debugging information. If I insert a printf into my backtrace code, and print out the addresses of each return address I see something like this: 0x406f25 0x407158 Function _Unwind_RaiseExcep...

...e this function) Unix/Path.inc:256: error: (Each undeclared identifier is reported only once for each function it appears in.) Unix/Path.inc:256: error: expected `;' before "DLInfo" Unix/Path.inc:257: error: `DLInfo' undeclared (first use this function) Unix/Path.inc:257: error: `dladdr' undeclared (first use this function) make[1]: *** [/cygdrive/i/Projects/llvm/lib/System/Debug/Path.o] Error 1 make[1]: Leaving directory `/cygdrive/i/Projects/llvm/lib/System' make: *** [all] Error 1 I have svn revision 48243, a relatively recent cygwin (1.5.24-2) with gcc 3.4.4 (i.e. no...

Seems like this in 83986 [1] needs a fix in Lapack.c: if (dladdr((void *) F77_NAME(ilaver), &dl_info)) { char buf[PATH_MAX+1]; char *res = realpath(dl_info.dli_fname, buf); if (res) { SEXP nfo = R_NilValue; if (strstr(res, "flexiblas")) nfo = R_flexiblas_info();...

> ISSUE: In Interpreter::getCurrentExecutablePath(), dladdr() is a > Solarisism. Luckily, getCurrentExecutablePath isn't being currently > used anywhere in lli. It looks like under my linux box, the dladdr prototype is wrapped with a #ifdef __USE_GNU option... If so, perhaps the write patch is to add -DGNU-SOURCES (or whatever that option is)...

...not included implicitly and so linking fails. Although I believe this is a bug in GCC 9, as a workaround use dlsym as the sentinel function instead. The new output from ‘./configure CFLAGS="-fsanitize=address"’ is: checking for library containing dlsym... -ldl [...] checking for dladdr... yes See also: https://bugzilla.redhat.com/show_bug.cgi?id=1702761 --- configure.ac | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/configure.ac b/configure.ac index 4624bf8..1d3aa7b 100644 --- a/configure.ac +++ b/configure.ac @@ -224,11 +224,11 @@ AS_IF([test &quot...

...'t be as easy as C for C functions. What I was really looking for was a way to create a Function object from a function pointer. I think I understand why it can't be that simple (LLVM really needs a function name, and function pointers don't have that) so I've made a funny hack with dladdr to get the name of a method at runtime, but just in case I really missed something I'll ask you guys: is there a "standard", LLVM-backed way to make a Function object from a function or method with C++ linkage? (I know I could also make an extern "C" function to wrap the cal...

...ix/Path.inc:256: error: (Each undeclared identifier is reported only > once for each function it appears in.) > Unix/Path.inc:256: error: expected `;' before "DLInfo" > Unix/Path.inc:257: error: `DLInfo' undeclared (first use this function) > Unix/Path.inc:257: error: `dladdr' undeclared (first use this function) > ... > Any ideas? What LLVM is trying to do here is determine its own path. I don't know if the approach being used will work on Cygwin. (The code is very new, and it's never worked on Cygwin.) You could try reading the /proc/$$/exe symli...

...heavyweight, so the overhead of linking and loading the library shouldn't be too bad. For now, this can be achieved by rolling your own compilation pipeline of: 1. run llc or the equivalent to make a .s in a temp dir 2. assemble it 3. link it to make a dylib in the temp dir 4. dlopen it 5. use dladdr to get the function pointer for your code 1 and 2 can already be done in memory with LLVM. 3 cannot, and doesn't look like it is on anyone's roadmap. I think 4 may become possible on OS X, and there's this feature request for glibc that essentially implements "dlopen from memory...

...-- Looking for strerror -- Looking for strerror - found -- Looking for strerror_r -- Looking for strerror_r - found -- Looking for strerror_s -- Looking for strerror_s - not found -- Looking for setenv -- Looking for setenv - found -- Looking for dlopen -- Looking for dlopen - found -- Looking for dladdr -- Looking for dladdr - not found -- Performing Test HAVE_STRUCT_STAT_ST_MTIMESPEC_TV_NSEC -- Performing Test HAVE_STRUCT_STAT_ST_MTIMESPEC_TV_NSEC - Failed -- Performing Test HAVE_STRUCT_STAT_ST_MTIM_TV_NSEC -- Performing Test HAVE_STRUCT_STAT_ST_MTIM_TV_NSEC - Success -- Looking for __GLIBC__ --...