search for: myfunc3

...elim bt.ll -o bt.S $ gcc -fno-omit-frame-pointer bt.S -o bt-llc $ ./bt-llc 4 backtrace() returned 1 addresses ./bt-llc() [0x4007f0] $ cat bt.c #include <execinfo.h> #include <stdio.h> #include <stdlib.h> #include <unistd.h> void myfunc3(void) { int j, nptrs; #define SIZE 100 void *buffer[100]; char **strings; nptrs = backtrace(buffer, SIZE); printf("backtrace() returned %d addresses\n", nptrs); /* The call backtrace_symbols_fd(buffer, nptrs...

Hi James, We've indeed passed the appropriate (and even excessive) flags to the appropriate pipeline parts, that is: llvm-gcc -O1 -fno-omit-frame-pointers -g $in -emit-llvm -S -o $name.ll llc --disable-fp-elim $name.ll -o $name.S g++ -fno-omit-frame-pointers -c $name.S , but that didn't work Alex On Tue, Apr 5, 2011 at 4:40 PM, James Molloy <James.Molloy at arm.com> wrote:

Dear all, I'm writing a lgrind definition for R. Lgrind is a program to produce pretty program listings for inclusion in LaTeX documents. Does anybody here have any experience with lgrindefs? My definition now looks like this: R:\ :pb=^\d?\p\d<-\dfunction\(\a\):\ :bb={:be=}:cb=\d#:ce=$sb=":se=\e":lb=':le=\e':id=.:\ :zb=@:ze=@:tb=%%:te=%%:mb=%\$:me=\$%:vb=%\|:ve=\|%:\

Dear all, I'm writing a lgrind definition for R. Lgrind is a program to produce pretty program listings for inclusion in LaTeX documents. Does anybody here have any experience with lgrindefs? My definition now looks like this: R:\ :pb=^\d?\p\d<-\dfunction\(\a\):\ :bb={:be=}:cb=\d#:ce=$sb=":se=\e":lb=':le=\e':id=.:\ :zb=@:ze=@:tb=%%:te=%%:mb=%\$:me=\$%:vb=%\|:ve=\|%:\