similar to: Crash with Unicode and sub (PR#14114)

Displaying 20 results from an estimated 2000 matches similar to: "Crash with Unicode and sub (PR#14114)"

2009 Dec 10
1
Antwort: Re: Crash with Unicode and sub (PR#14114)
I don't know about the technicalities, but Peter Dalgaard said the offending code also causes R to come to a stop using SUSE + WINE. Is it possible to run that lot on top of valgrind? Of course, it will probably take all day ... If not, I have a clue which might help. The problem seems to lie in the "sub" routine. In the original report I used -- cut here -- gctorture() u <-
2009 Nov 16
3
R crash with intToUtf8 on huge vectors (PR#14068)
Full_Name: George Russell Version: 2.10.0 OS: Windows XP Professional Version 2002 Service Pack 2 Submission from: (NULL) (217.111.3.131) Typing the following command into R --vanilla causes R to crash: k <- intToUtf8(rep(1e3,1e7)) This is the output of sessionInfo(): R version 2.10.0 (2009-10-26) i386-pc-mingw32 locale: [1] LC_COLLATE=German_Germany.1252 LC_CTYPE=German_Germany.1252
2010 Feb 09
3
Confusing error message for [[.factor (PR#14209)
Full_Name: George Russell Version: 2.10.0 and 2.11.0 Under development (unstable) (2010-02-08 r51108) OS: Windows Submission from: (NULL) (217.111.3.131) > c("a","b")[[c(TRUE,FALSE)]] Error in `[[.default`(factor(c("a", "b")), c(TRUE, FALSE)) : recursive indexing failed at level 1 I find this error message confusing, though after reading the HELP
2010 Feb 19
3
Rubbish values written with zero-length vectors (PR#14217)
Full_Name: George Russell Version: 2.10.0, 2.11.0 (2009-12-13 r50716) OS: Windows Submission from: (NULL) (217.111.3.131) R trace: -- cut here -- > v <- integer(0) > v[[1]] <- v > v [1] 20522144 > v <- numeric(0) > v[[1]] <- v > v [1] 4.254131e-314 > sessionInfo() R version 2.10.0 (2009-10-26) i386-pc-mingw32 locale: [1] LC_COLLATE=German_Germany.1252
2009 Oct 13
2
Sweave output encoding in R-2.10.0beta on Windows (Rgui <-> Rterm)
Dear developers, I have come across a (somewhat strange) change in the encoding of Sweave output from R-2.9.2pat to R-2.10.0beta (apparently specific to Rgui) on Windows installations. Of course, the NEWS file contains quite a few changes concerning encoding, but I was not able to locate an entry which explains the observed behaviour. I am not very familiar with encodings/locales/codepages,
2009 Dec 29
1
problem reading from serial connection since 2.10.0
Dear list, I have a balance connected to the serial port of a windows machine ("COM1") and I read the text output of the balance with scan("COM1", what="character", sep="\n", n=1) after calling the previous line I press the print key on the balance which triggers sending one line of text to the serial connection and with R 2.9.2 I get something like Read
2009 Jan 30
1
Methods not loaded in R-Devel vs 2.8.1
Dear list-member, I am currently developing a package with S4 classes. The NAMESPACE and DESCRIPTION is printed below. Within this package I have set a method "residuals" for two classes. In version 2.8.1 these two are reported whereas in R-Devel (2009-01-28 r47766). What have I missed? What has changed and how can I rectify the issue? Your help and pointers are welcome. For 2.8.1:
2006 Oct 27
2
all.names() and all.vars(): sorting order of functions' return vector
Dear list-subscriber, in the process of writing a general code snippet to extract coefficients in an expression (in the example below: 0.5 and -0.7), I stumbled over the following peculiar (at least peculiar to me:-) ) sorting behaviour of the function all.names(): > expr1 <- expression(x3 = 0.5 * x1 - 0.7 * x2) > all.names(expr1) [1] "-" "*" "x1"
2011 Apr 21
3
R CMD Sweave versus Sweave() on Windows
Dear list subscriber, I am quite puzzled by the behaviour of processing Sweave files within an R session, i.e. Sweave("foo.Rnw") versus R CMD Sweave foo.Rnw In the former the environmental variable 'SWEAVE_STYLEPATH_DEFAULT = TRUE' is obeyed (this is set in etc/Renviron.site as well as under the users home directory in .Renviron). That is the hard-coded path to Sweave.sty is
2007 May 01
1
integer constants given by hexadecimal notation
Hi, > 0x10L returns: int 0 I would expect: int 16? This happens with all integer constants given by hexadecimal notation. It's a bug? > sessionInfo() R version 2.5.0 (2007-04-23) i386-pc-mingw32 locale: LC_COLLATE=German_Germany.1252;LC_CTYPE=German_Germany.1252;LC_MONETARY=German_Germany.1252;LC_NUMERIC=C;LC_TIME=German_Germany.1252 attached base packages: [1] "stats"
2008 May 09
1
comparison (PR#11421)
In R-2.7.0 release as well as patched (from yesterday) under Windows XP, R crashes when typing, e.g.: repeat{ rep(1, 10000) == "?" } Note that I cannot reproduce the error in R-2.6.2 nor R-devel. Uwe Ligges --please do not edit the information below-- Version: platform = i386-pc-mingw32 arch = i386 os = mingw32 system = i386, mingw32 status = major = 2 minor =
2009 Jan 27
1
small bug in base::formatC (PR#13474)
Full_Name: Bernd Bischl Version: 2.8.1 OS: Windows XP Professional Submission from: (NULL) (129.217.207.95) Hi, there seems to be a small bug in formatC: formatC("foo", format="s", mode="charcacter") Error in formatC("foo", format = "s", mode = "charcacter") : 'mode' must be "double" ("real") or
2011 Mar 21
1
error in: testing if installed package can be loaded
hi, I am preparing my package for R 2.13 build and check gives no warnings just OK's However when running R CMD INSTALL it gives me (nfortunately it is in german) ** help *** installing help indices ** building package indices ... ** testing if installed package can be loaded Fehler: '\U' ohne Hex-Ziffern in der Zeichenkette beginnend mit "C:\U" genutzt Ausführung
2013 Sep 13
1
numerical issue in contour.default?
Dear R developers, I found a small issue while plotting contours of data containing both "usual" and "very small" numbers. It appeared with both R 3.0.1 and R-Devel on Windows, and I could reproduce it on Linux. Would it be possible to solve this before the upcoming release? Thanks a lot for developing this great software! Thomas Example: ######## set.seed(357) z1 <-
2007 May 01
2
integer constants given by hexadecimal notation (PR#9648)
On 01/05/2007 7:21 AM, Stephan wrote: > Hi, > >> 0x10L > returns: int 0 > > I would expect: int 16? > This happens with all integer constants given by hexadecimal notation. > It's a bug? Certainly looks like one; I've cc'd this to the bug list (but won't be able to look into fixing it). Duncan Murdoch > > >> sessionInfo() > R
2008 Dec 18
2
lme4 error after Matrix update
Dear all, after recently updating my R-packages I am unable to work with lme4, since it does not load. What I get is this: Error in inDL(x, as.logical(local), as.logical(now), ...) : function 'cholmod_l_start' not provided by package 'Matrix' In addition: Warning messages: 1: package 'lme4' was built under R version 2.8.1 2: package 'lattice' was built under R
2008 May 01
1
Locale problem with umlauts in factor levels in 2.7.0 (patched) from grid or lattice
With 2.7.0 patched (not tested with 2.0.0), I get an error message in a program that ran correctly in R 2.6.2 when the grouping factor of a stripplot contains an Umlaut: I am aware that there are a few locale-changes in R 2.7.0, but I could not easily locate who's at fault Dieter library(lattice) dt = data.frame(x=rnorm(100),y=1:100,levs= as.factor(c("Gru","Gr?")))
2007 May 14
1
optim bug (PR#9684)
Full_Name: Christina Merz Version: R version 2.5.0 (2007-04-23) OS: mingw32 Submission from: (NULL) (213.70.209.132) R> version _ platform i386-pc-mingw32 arch i386 os mingw32 system i386, mingw32 status
2007 Jun 15
2
Problem with workspace loading after languageR use
Hello R, To analyze multi-level data, I started learning and using lmer. So far so wonderful. I then found some useful functions in package languageR. But then the following problem ocurred: Whenever I load and use the languageR package, then save the workspace - or quit R with saving the workspace - I am unable to reload that workspace in a later session. That is, R doesn't start at all
2011 Apr 14
1
Possible bug in 'relist()' and/or 'as.relistable()'
Dear list, I think I just stumbled across a bug in either 'relist()' and/or 'as.relistable()'. It seems that 'pairlists' can only be un- and relisted as long as they're not nested: Good: a <- as.relistable(as.pairlist(list(a=1, b=2))) a <- unlist(a) relist(a)# Works Bad: a <- as.relistable(as.pairlist(list(a=1, b=2, c=list(c.1=1, c.2=2)))) a <- unlist(a)