similar to: [LLVMdev] Debugging LLVM IR with GDB

> Has anybody debugged LLVM IR with GDB? I'm using dragonegg to transform C > into IR, then applying my optimizations. Passing "-g" to dragonegg doesn't > seem to work since it generates debug info for the C code, not the IR. I > really need GDB (lli doesn't solve my problems) in order to debug > multi-threaded and multi-process MPI code. > > More

Hi Pablo, > Has anybody debugged LLVM IR with GDB? I'm using dragonegg to transform C into > IR, then applying my optimizations. Passing "-g" to dragonegg doesn't seem to > work since it generates debug info for the C code, not the IR. I really need GDB > (lli doesn't solve my problems) in order to debug multi-threaded and > multi-process MPI code. > >

On Thu, Oct 18, 2012 at 8:59 AM, Eli Bendersky <eliben at gmail.com> wrote: > >> Has anybody debugged LLVM IR with GDB? I'm using dragonegg to transform C >> into IR, then applying my optimizations. Passing "-g" to dragonegg doesn't >> seem to work since it generates debug info for the C code, not the IR. I >> really need GDB (lli doesn't

Duncan Sands wrote: > Hi Pablo, > > > Has anybody debugged LLVM IR with GDB? I'm using dragonegg to transform C into > > IR, then applying my optimizations. Passing "-g" to dragonegg doesn't seem to > > work since it generates debug info for the C code, not the IR. I really need GDB > > (lli doesn't solve my problems) in order to debug

Hello, I'd like to take a look at how the taskPR package performs on our computational cluster, and this morning I've spend some time trying to do a test install of this package on one of our linux machines. Unfortunately I've been unsuccessful in completing the install, and I wondered if someone could please advise me. As I've noted I working on a linux machine, and it's

Hello, We have recently added a 64-bit 2 x Dual-Core Athlon server running Red Hat Enterprise Linux AS release 3 to allow for processing of large data sets (>4GB) in R. To integrate this server into our Linux cluster, I have been trying (unsuccessfully) to use Rmpi/lam-mpi to parallel process some of our scripts. While I have successfully compiled R 2.4.0 and lam-mpi 7.1.2 on this server using

One way to deal with this is to install R itself with mpicc. Then all packages are installed with mpicc and get the required MPI libraries and includes by default. I have done this with R-2.13.0 on an Opteron cluster running CentOS-5 a while ago and so far it has worked out great. I crosspost to r-sig-hpc and welcome others to comment if there are potential downsides to this solution. George

Dear R Debian Users: I wrote a quick C program (eventually to become R code) and compiled it as: mpicc -o greet greet.c So far so good. Now when I run mpirun, this happens: erin at erin-laptop:~$ mpirun -np 2 greet ----------------------------------------------------------------------------- It seems that there is no lamd running on the host erin-laptop. This indicates that the LAM/MPI

I am running into the following issue that has been previously reported on the R-devel mailing list. The short version is that I'm writing a package for MPI, and I'd like to change CC and SHLIB_LD to "mpicc". Trying to change them in Makevars.in has no effect, because the values are clobbered by /etc/R/Makeconf. Will the following changes to Makeconf.in introduce any problems?

I'm trying to run the example described at: http://llvm.org/docs/DebuggingJITedCode.html I followed the sample command line session (below, with versions numbers for everything), but gdb doesn't stop at the breakpoints as described. Any idea what is wrong? Thanks, Zach zdevito at derp:~/terra/tests$ > ~/clang+llvm-3.4-x86_64-unknown-ubuntu12.04/bin/clang -cc1 -O0 -g >

According to http://llvm.org/docs/DebuggingJITedCode.html only ELF objects are supported for gdb support of JIT generated code. Is this still true, or are Mach-O files now supported in 2.7 trunk? Thanks in advance Garrison

I run some code in JIT on x86-64 architecture. Even though llvm::NoFramePointerElim is set to true, I still see weird stack in gdb, see below. 800b485a4 is the current rip register where gdb stopped. Then many others values aren't valid. Then there is value that looks ok again. Why gdb can't determine stack? Yuri -- stack -- #0 0x0000000800b485a4 in ?? () #1 0x000000000000005f in

I know you haven't been able to get the JIT gdb support to work on FreeBSD (right?), but this is exactly the problem that we ran into that it solves. http://llvm.org/docs/DebuggingJITedCode.html I don't know what heuristic gdb is trying to use to unwind the stack, but it doesn't work. I asked a gdb developer about it two summers ago when I was working on this, but he seemed

Many thanks to Dr Yu for updating Rmpi for R 2.6.0, and for starting to make the changes to support Open MPI. I have just built the updated Debian package of Rmpi (i.e. r-cran-rmpi) under R 2.6.0 but I cannot convince myself yet whether it works or not. Simple tests work. E.g. on my Debian testing box, with Rmpi installed directly using Open Mpi 1.2.3-2 (from Debian) and using 'r' from

Hi, I need a simple demonstration of compiling a program into a executable which could be debugged using gdb. After looking up the llc.cpp, llvm-ld.cpp, I found that llvm only generated the assemble code, and left the other work to gnu as and gnu ld. Since the information from LLVM into gnu as and gnu ld is limited by the assemble file, I am confusing with how to transfer the debug information to

I have followed http://llvm.org/docs/DebuggingJITedCode.html, used the latest release gdb-7.1 (from March 18, 2010) and got this stack: (gdb) bt #0 0x35532156 in ?? () #1 0x355320f8 in ?? () #2 0x35532098 in ?? () #3 0x3553202e in ?? () #4 0x34a5661a in ?? () #5 0x349d9bd9 in ?? () #6 0x08052cd9 in main (argc=4, argv=0xbfbfe264, envp=0xbfbfe278) at

Hello, I try to install pbdMPI. Compilation successful, but load fails with segfault. Is anyone can help me? R version 3.0.0 pbdMPI version 0.1-6 Intel compiler version 13.1.1 OpenMPI version 1.6.4-1 CPU Intel x86_64 # R CMD INSTALL pbdMPI_0.1-6.tar.gz .. .... checking for gcc... icc -std=gnu99 checking whether the C compiler works... yes checking for C compiler default output file name...

Hi, I’m wondering if it’s possible to debug code JIT’ed with the newer ORC JIT. The LLVM documentation has a page at llvm.org/docs/DebuggingJITedCode.html <http://llvm.org/docs/DebuggingJITedCode.html> showing an example of using gdb to debug MCJIT’ed code, but has no mention of ORC JIT. From searching around online I’ve gotten the impression that ORC JIT does *not* support providing

Hello, is there any way to debug a program in LLVM-IR line-by-line (i.e. with gdb)? The problem is, i have a program in human-readable-intermediate representation that segfaults, when executed. I want to know, which line in the IR causes this. Any help is appreciated. Best regards, Sebastian

I am working on a SLES 10 cluster with R available on it. To better use my resources, I want to use Rmpi, but I am having a difficult time installing it. I have set the $R_LIBS variable correctly. The MPI libraries are available through the PGI compiler, but this R instance was compiled with GCC. The Rmpi package can be compiled and installed with %R CMD INSTALL Rmpi_0.5-5.tar.gz