Skip to content
Prev 165058 / 398503 Next

"Error: bad value" problem

Ben Bolker wrote:
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 
../../../R/src/main/errors.c:704
#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 
gram.y:958
#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?