[R] [Rd] "Error: bad value" problem
murdoch at stats.uwo.ca
Thu Dec 18 04:07:04 CET 2008
On 17/12/2008 9:47 PM, Duncan Murdoch wrote:
> On 17/12/2008 8:56 PM, Peter Dalgaard wrote:
>> 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
>>> odd going on with the plots.)
>>> Hope that helps someone ...
>> Probably not. The problem is to reproduce the error state in a way so
>> that we can understand what is causing it.
>> I can debug this to
>> (gdb) bt
>> #0 Rf_error (format=0x8220c65 "bad value") at
>> #1 0x0805a924 in SETCDR (x=0x8f89348, y=0x9b276e8)
>> at ../../../R/src/main/memory.c:2728
>> #2 0x0819fa46 in GrowList (l=0x951e8f4, s=<value optimized out>) at
>> #3 0x081a2a7b in xxvalue (v=0x8f89348, k=4, lloc=<value optimized out>)
>> at gram.y:440
>> and the problem in GrowList is that CAR(l) is R_NilValue (==0x8f89348),
>> which supposedly "cannot happen", and the thing that calls GrowList is
>> something with srcrefs (DuncanM?).
>> Digging deeper probably has to wait till the weekend for my part. (The
>> natural next step is figuring out how the R_NilValue got into that
>> location, but I should try to sleep off this cold....)
>> I'm CCing r-devel on this. Can we move the discussion there?
> I can probably take a look tomorrow. I wasn't getting an error, but
> maybe I'll see the same corruption if I watch it run.
I had time to see if I was getting a NilValue there tonight, and the
answer was no, with the Windows RC. I don't get the error in any
version I've tried on Windows, though I can see it in 2.8.0 on MacOSX.
> Duncan Murdoch
>>> Ben Bolker
>>> R version 2.8.0 (2008-10-20)
>>> attached base packages:
>>>  stats graphics grDevices utils datasets methods base
> R-devel at r-project.org mailing list
More information about the R-help