similar to: uninitialised value in R (PR#13476)

Hi, Please see the email exchanges below. I am having trouble generating output that is large enough for our needs, specifically when using the GaussRF function. However, when I wrote Dr. Schlather (the author of the GaussRF function), he indicated that there is also a limit imposed by R itself. Is this something that we can overcome? Thank you very much for any assistance you may provde.

Martin Maechler asked me to restate my problem. Compiling the file (slightly modified w.r.t. the formerly attached file) that can be found at http://www.geo.uni-bayreuth.de/~martin/filetransfer/xswms2d.Rd terminates with the error message ******* Syntax error: mismatched or missing brackets in /----- ..... \----- when compiled by R CMD Rdconv -t txt xswms2d.Rd However, the file does

Hi, I have problems when calling fft_factor and fft_work directly in my C-code. Martin Maechler already told me that I should not do this -- anyway, the code works fine if the length of the vector is a multiple of 2,3,5. If the length of the vector has different form I get, in some cases, a segmentation fault when work and iwork are freed (I use C's malloc to allocate memory for work and

Dear R Core Team, I'm wondering whether it is useful that every package should allow for help(PackageName), giving some general information about the package (more/nicer than library(help=PackageName)). This man page may include some mathematical or statistical background, or contain a guideline for the package. Cheers, Martin -- Martin Schlather email:

Hi, I have attached a larger Rd file that causes an error when compiled by R CMD Rdconv -t txt xswms2d.Rd (for example). If the size is reduced the error vanishes, see the lines 230 and 527 in the file. I could not find an error within my text and so my guess is that there is some buffer overflow within the compiler. If it is me who has caused the error please let me know -- and many

Dear all, (sorry I got the wrong button for subscribing a minute ago) At the moment I'm writing on a package for random field simulation that I'd like to make publically availabe in near future. To this end I've asked Martin Maechler to have a look at my R-code. He was very surprised about how I perform the ".C"-calls, and encouraged me to make this request for comments.

The code has s = INT_MAX; for (i = 0; i < n; i++) { if (x[i] != NA_INTEGER) { if (s > x[i]) { s = x[i]; if(!updated) updated = 1; } } else if (!narm) { if(!updated) updated = 1; *value = NA_INTEGER; return(updated); } } *value = s; so it ignores the initial value INT_MAX (updated is not set). Fairly easy to fix ... done for

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 in R are now only referenced whenever possible and not always copied; hence .C(...,

Hi, The help for `assign' says In all the assignment operator expressions, `x' can be a name or an expression defining a part of an object to be replaced (e.g., `z[[1]]'). The name does not need to be quoted, though it can be. So I would expect that by a<-1:4 assign("a[1]",2) the first component of a gets the value 2, but the object "a[1]" is

Dear all, I work with R Version 2.0.0 on Machine hardware: sun4u OS version: 5.9 Processor type: sparc Hardware: SUNW,Sun-Blade-1000 and I have a very simple data frame (called OR) with the following variables: > sapply( OR, class) X ci FTyp "factor" "numeric" "factor" (In OR$ci there are some Inf-values. OR's

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, 10^20) [1] 2147483647 > min(as.integer(.Machine$integer.max - 1), 10^20) [1] 2147483646 >

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 --- with valgrind ---- > sum(c(NA,1)[1]) [1] NaN R call with valgrind: R -d "valgrind --tool=memcheck

Dear all, Paulo Ribeiro, p.ribeiro@lancaster.ac.uk, and myself noticed that R sometimes breaks down with a segmentation fault of (at least for us) unknown course. (We've read #411 and #671 in the bug report on "optim" -- the problem described there sounds familiar; but we have not found any hint on a segmentation fault.) Please find at the very end of this email the file

Hello, R 4.0.2 on Ubuntu 20.04, sessionInfo at end. This came up in r-help, I'm answering to the OP and also posting to r-devel since I believe it is more appropriate there. I can confirm this. The original instructions are the first and the last, but even with smaller numbers the error shows up. set.seed(2020) jitter(c(1,2,10^4)) # desired behaviour #[1] 1.058761 1.957690

https://bugzilla.mindrot.org/show_bug.cgi?id=2500 Bug ID: 2500 Summary: ConnectionAttempts=0 causes ssh to output uninitialised data on stdout Product: Portable OpenSSH Version: 7.1p1 Hardware: amd64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: ssh

Hi, My Server runs on Ubuntu Server 12.04 LTS 32 bits. I'm getting the following error messages when I run "make check" during the compilation of dovecot-2.2.13. <snip> ==2058== Conditional jump or move depends on uninitialised value(s) ==2058==??? at 0x4049DD8: inflateReset2 (in /lib/i386-linux-gnu/libz.so.1.2.3.4) ==2058==??? by 0x4049EC7: inflateInit2_ (in

Hi, Ralph recently checked in a version of theora/tests/noop.c that uses the new API. Part of the reason for this test is to check for memory leaks in the library's constructors and destructors. You can run the test suite under valgrind by configuring with --enable-valgrind-testing. The test passes, but gives output like: make[1]: Entering directory

Hi, I'm using valgrind to check over some C/C++ code for an R library. I'm getting the report (see below), but can't track down the uninitialised value(s). I tried using --track-origins=yes in valgrind which gives: ==28258== Uninitialised value was created by a stack allocation ==28258== at 0xEE33D98: ??? (in /usr/lib64/R/lib/libRlapack.so) I presume the problem is an

Hello, I am currently using Dovecot 2.2.10 on Fedora 16 - 64 bit system I had made v2.2.10 Fedora 16 rpm file using spec file from ATrpms. http://dl.atrpms.net/all/dovecot.spec It has been working well from 6 months or so. Today I tried to make v2.2.15 rpm using same spec file. But "make check" is giving following error: fatal_printf_format_fix

Hi. I''m having problems with a class constant I''ve defined as follows: class Customer < ActiveRecord::Base has_many :orders TITLES = [''Mr'', ''Ms'', ''Miss'', ''Mrs''] end Whenever I try and access this constant using Customer::TITLES, I get an unitialized constant Customer::TITLES error. Is my syntax