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.)

  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 ../../../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?




  Ben Bolker

sessionInfo()
R version 2.8.0 (2008-10-20) i486-pc-linux-gnu
locale:
LC_CTYPE=en_US.UTF-8;LC_NUMERIC=C;LC_TIME=en_US.UTF-8;LC_COLLATE=en_US.UTF-8;LC_MONETARY=C;LC_MESSAGES=en_US.UTF-8;LC_PAPER=en_US.UTF-8;LC_NAME=C;LC_ADDRESS=C;LC_TELEPHONE=C;LC_MEASUREMENT=en_US.UTF-8;LC_IDENTIFICATION=C

attached base packages:
[1] stats graphics grDevices utils datasets methods base


--
   O__  ---- Peter Dalgaard             Ă˜ster Farimagsgade 5, Entr.B
  c/ /'_ --- Dept. of Biostatistics     PO Box 2099, 1014 Cph. K
 (*) \(*) -- University of Copenhagen   Denmark      Ph:  (+45) 35327918
~~~~~~~~~~ - (p.dalga...@biostat.ku.dk)              FAX: (+45) 35327907

______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

Reply via email to