by Ben Bolker Dec 18, 2008; 01:36am :: Rate this Message:
I can get the errors to happen on Ubuntu 8.10 with R --vanilla
(*without* valgrind) -- but editing momfit.r line 742 so that
plot.progress=FALSE seems to make the problem go away. (This was a
lucky guess, it looked like there was s
Ben Bolker wrote:
I can get the errors to happen on Ubuntu 8.10 with R --vanilla (*without*
valgrind) -- but
editing momfit.r line 742 so that plot.progress=FALSE seems to make the
problem go away. (This was a lucky guess, it looked like there was
something
odd going on with the plots.)
Ho
I can get the errors to happen on Ubuntu 8.10 with R --vanilla (*without*
valgrind) -- but
editing momfit.r line 742 so that plot.progress=FALSE seems to make the
problem go away. (This was a lucky guess, it looked like there was
something
odd going on with the plots.)
Hope that helps someo
Peter Dalgaard wrote:
Rolf Turner wrote:
On 18/12/2008, at 11:34 AM, Richard E. Chandler wrote:
Dear R-help,
Like several other subscribers, I have recently encountered a problem
whereby R will execute code apparently correctly and without error,
but any subsequent command will yield "Error:
On 18/12/2008, at 1:09 PM, Peter Dalgaard wrote:
Rolf Turner wrote:
I can confirm that the error occurs.
I downloaded the files and sourced ``ErrorDemo.R''. Doing x <-
rnorm(10)
after doing so triggered the error. Subsequently attempting
traceback()
(or anything else) simply
On 17/12/2008 5:34 PM, Richard E. Chandler wrote:
Dear R-help,
Like several other subscribers, I have recently encountered a problem
whereby R will execute code apparently correctly and without error,
but any subsequent command will yield "Error: bad value" so that R
has to be killed and rest
Rolf Turner wrote:
On 18/12/2008, at 11:34 AM, Richard E. Chandler wrote:
Dear R-help,
Like several other subscribers, I have recently encountered a problem
whereby R will execute code apparently correctly and without error,
but any subsequent command will yield "Error: bad value" so that R
h
On 18/12/2008, at 11:34 AM, Richard E. Chandler wrote:
Dear R-help,
Like several other subscribers, I have recently encountered a problem
whereby R will execute code apparently correctly and without error,
but any subsequent command will yield "Error: bad value" so that R
has to be killed and
Dear R-help,
Like several other subscribers, I have recently encountered a problem
whereby R will execute code apparently correctly and without error,
but any subsequent command will yield "Error: bad value" so that R
has to be killed and restarted. We have checked this out with a few
differe
Dear R Users,
I am getting a strange error, also relayed by Jose Quesada about a year
ago. As below, in his message, I get "Error: bad value" to whatever I
enter into the R console.
My configuration is:
- Windows XP SP2
- R 2.7.2
Has this problem been tracked down to a specific package ? I a
I'm running R 2.7.1 on Windows XP. Lately and spontaneously, it will
give an "error: bad value" message in response to any command. I have
to restart R to (temporarily) fix the problem.
There are two other threads I've found on the issue here:
http://tolstoy.newcastle.edu.au/R/e4/help/08/01/075
Please don't multiple post:
https://stat.ethz.ch/pipermail/r-help/2008-January/150004.html
is the same message. As you didn't follow the posting guide, you did not
get a reply from me the first time (and nor it seems from anyone else).
On Fri, 11 Jan 2008, Sven Garbade wrote:
> Hi list,
>
> f
Sorry for sending my email twice, first I used
"[EMAIL PROTECTED]" and thought this was wrong. R version is
2.6.1 (2007-11-26).
Thanks, Sven
On Fri, 2008-01-11 at 10:16 +0100, Martin Maechler wrote:
> > "SG" == Sven Garbade <[EMAIL PROTECTED]>
> > on Fri, 11 Jan 2008 09:47:39 +0100 w
> "SG" == Sven Garbade <[EMAIL PROTECTED]>
> on Fri, 11 Jan 2008 09:47:39 +0100 writes:
SG> Hi list,
SG> from time to time I got an "Error: bad value" and must restart R. The
SG> mail archives suggests memory corruption, but I do not run "special" C
SG> code, only base
Hi list,
from time to time I got an "Error: bad value" and must restart R. The
mail archives suggests memory corruption, but I do not run "special" C
code, only base R calls.
I use R release 2.6.22 on a Debian GNU/Linux (version "testing") on a
i686 machine with 2 GB RAM, kernel version 2.6.22.
Hi list,
from time to time I got an "Error: bad value" and must restart R. The
mail archives suggests memory corruption, but I do not run "special" C
code, only base R calls.
I use R release 2.6.22 on a Debian GNU/Linux (version "testing") on a
i686 machine with 2 GB RAM. R was installed with d
16 matches
Mail list logo
