[Rd] memory leak in split.screen

2016-07-18 Thread Martin Schlather via R-devel
-07-15 r70918) nickname Unsuffered Consequences I would be happy to get any hint that explains this behaviour. The LeakSanitizer message appears in the interactive mode, but not in the batch mode. With kind regards, Martin Schlather

[Rd] different behaviour of NAs under valgrind (PR#14171)

2009-12-28 Thread schlather
Full_Name: Martin Schlather Version: 2.10.0 OS: linux Submission from: (NULL) (91.3.220.231) Bug summary: some functions behave differently for NAs when valgrind is used in R, e.g. sum and prod Bug demonstration: --- without valgrind sum(c(NA,1)[1]) [1] NA

Re: [Rd] uninitialised value in R (PR#13476)

2009-01-28 Thread Martin Schlather
Mathieu, I do not understand what you mean in your email. I am only interested in the cause of the valgrind message in .Call(XXX) [1] 1 nd - 3 solve(diag(nd) , as.vector(1:nd)) [1] 1 2 3 .Call(XXX) ==25734== Conditional jump or move depends on uninitialised value(s) ==25734==at

[Rd] documentation of .C (PR#9948)

2007-10-10 Thread schlather
Full_Name: Martin Schlather Version: R version 2.7.0 Under development (unstable) (2007-10-01 r43043) OS: Linux Submission from: (NULL) (91.3.209.203) Hi, There are 2 dangers with using 'DUP=FALSE' mentioned: * formal arguments * lists Would you also mention a third one, namely that values