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
--- w
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
t
SAGES=en_GB.UTF-8;LC_PAPER=en_GB.UTF-8;LC_NAME=C;LC_ADDRESS=C;LC_TELEPHONE=C;LC_MEASUREMENT=en_GB.UTF-8;LC_IDENTIFICATION=C
Search Path:
.GlobalEnv, package:stats, package:graphics, package:grDevices,
package:utils, package:datasets, package:methods, Autoloads, package:base
--
Prof. Dr.
Full_Name: Martin Schlather
Version: 2.2.0 and alpha 2.3.0 (06/3/29)
OS: Linux (x86_64 and Intel)
Submission from: (NULL) (139.11.183.106)
> min(.Machine$integer.max, 10^20)
[1] 1e+20
> min(as.integer(.Machine$integer.max), 10^20)
[1] 1e+20
but
> min(.Machine$integer.max + 0,
status = Under development (unstable)
>> major = 2
>> minor = 9.0
>> year = 2009
>> month = 01
>> day = 13
>> svn rev = 47573
>> language = R
>> version.string = R version 2.9.0 Under development (unstable)
>> (2009-01-13 r47573)
>
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 0
-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