similar to: How to explore R internals through gdb?

I'm very green with R, so maybe this is not a bug, but it looks like one to me. The following program segfaults at the second call to Rf_PrintValue(). To failure depends on the value of the y-string. E.g., if I change it from "coverage" to, say, "COVERAGE", the segfault does not occur. /* bug.c */ #include <stdio.h> #include <Rinternals.h> #include

Consider the following simple C program: /*** hello_r.c ***/ #include <Rinternals.h> SEXP hello() { return mkString("Hello, world!\n"); } int main(void) { SEXP x = hello(); return x == NULL; /* i.e. 0 on success */ } This program segfaults: % myR/bin/R CMD LINK gcc -I./R-2.9.0/src/include -L./myR/lib64/R/lib -lR hello_r.c -o hello_r > /dev/null % hello_r zsh:

Hi Kynn, Thanks for expanding. I wrote a function like yours when I first started using R. It's basically the same up to your "new.env()" line, I don't do anything with environmentns. I just called my function "mysource" and it's essentially a "source with path". That allows me to find code I reuse in standard locations. I don't know why R does not

On 10/03/2016 01:51 PM, Kynn Jones wrote: > Thank you all for your comments and suggestions. > > @Frederik, my reason for mucking with environments is that I want to > minimize the number of names that import adds to my current > environment. For instance, if module foo defines a function bar, I > want my client code to look like this: > > import("foo") >

Thank you all for your comments and suggestions. @Frederik, my reason for mucking with environments is that I want to minimize the number of names that import adds to my current environment. For instance, if module foo defines a function bar, I want my client code to look like this: import("foo") foo$bar(1,2,3) rather than import("foo") bar(1,2,3) (Just a personal

On Mon, Oct 3, 2016 at 10:18 AM, <frederik at ofb.net> wrote: > Hi Kynn, > > Thanks for expanding. > > I wrote a function like yours when I first started using R. It's > basically the same up to your "new.env()" line, I don't do anything > with environmentns. I just called my function "mysource" and it's > essentially a "source

Dear All, We are running RHEL4 Update 4 AS IA-64 on a HP rx6600. We are running programs compiled in RHEL4 Update 4 AS in i386 architecture using the emul library(Intel IA-32 Execution Layer ) [admin at corviewsecondary ~]$ service ia32el status Intel IA-32 Execution Layer in use When we attempt to run a program using /usr/bin/gdb we are not able to hit the break point set. [admin at

Hi, everyone. I'm trying to debug an R-module, written in C, and I'm using gdb for this. How can I print "standard" R objects from within C code? BTW, I'm familiar with the advice to use R_PV given in Writing R Extensions, but it's not working for me. E.g., I get (gdb) p R_PV(x) $1 = void and yet (gdb) p *x $2 = {sxpinfo = {type = 16, obj = 0, named = 0, gp = 0,

Hi Frederick, I described what I meant in the post I sent to R-help (https://stat.ethz.ch/pipermail/r-help/2016-September/442174.html), but in brief, by "zero overhead" I mean that the only thing needed for library code to be accessible to client code is for it to be located in designed directory. No additional meta-files, packaging/compiling, etc. are required. Best, G. On Sun, Oct

On Apr 23, 2012, at 2:14 PM, Roland Leißa <leissa at cs.uni-saarland.de> wrote: >>> ok, I now have a problem in the code generator. >>> Let's say I want to set a breakpoint somewhere in >>> clang/lib/CodeGen/CGExprScalar.cpp >>> >>> What do I have to do in order to trigger breakpoints, see >>> backtraces and so on? >>

Hi Jim, thanks for replying. As mentioned in my earlier mail, I have to specify -emit-obj along with -cc1 in order to trigger codegen. This solves the problem for me. As I learned from the last email, specifying -v is a good starting point in order to see what actually is happening and tackle such problems. -- Roland ----- Original Message ----- > From: "Jim Grosbach"

I'm having trouble debugging x86 code generated by LLVM. GDB does work with the code, but not correctly, for example, the "next" command does not skip over a function call. Here's an example. Source program gdb1.c: int x; void foo(){ x++; } void bar(){ x--; } int main(){ foo(); bar(); return 0; } commands: $ llvm-gcc -g -emit-llvm -c gdb1.c -o gdb1.bc $ llc

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 >

I'm an experienced programmer, but learning R is making me lose the little hair I have left... > list(NULL) [[1]] NULL > length(list(NULL)) [1] 1 > x <- list() > x[[1]] <- NULL > x list() > length(x) [1] 0 >From the above experiment, it is clear that, although one can create a one-element list consisting of a NULL element, one can't get the same result by

Hi, We have the error below. Any ideas ? Regards, Matt $ R --vanilla -d gdb GNU gdb 6.7.1-debian Copyright (C) 2007 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying"

> > ok, I now have a problem in the code generator. > > Let's say I want to set a breakpoint somewhere in > > clang/lib/CodeGen/CGExprScalar.cpp > > > > What do I have to do in order to trigger breakpoints, see > > backtraces and so on? > > You set a breakpoint and ask to see a backtrace? > > -eric haha, OK, I think I should be more specific.

Pranav Garg wrote: > Hi, > > I am trying to debug my llvm pass called -aa-eval-garg11 using gdb. > However I am not able to establish a breakpoint in any function of my > pass. I have compiled my > pass with a debug build and I have also compiled the input file (using > llvm-gcc) with the -g flag. Given below is the exact output. > > > (gdb) break

Hi, I am trying to debug my llvm pass called -aa-eval-garg11 using gdb. However I am not able to establish a breakpoint in any function of my pass. I have compiled my pass with a debug build and I have also compiled the input file (using llvm-gcc) with the -g flag. Given below is the exact output. (gdb) break llvm::PassManager::run Breakpoint 1 at 0x86be87c: file

Hi John, Yes, it was the problem of the namespace. Sorry for bugging for such a silly mistake. Thanks Pranav On Mon, Apr 19, 2010 at 9:33 AM, John Criswell <criswell at uiuc.edu> wrote: > Pranav Garg wrote: > >> Hi, >> >> I am trying to debug my llvm pass called -aa-eval-garg11 using gdb. >> However I am not able to establish a breakpoint in any function of

On Sat, Jun 19, 2010 at 8:53 PM, Yuri <yuri at rawbw.com> wrote: > 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