Re: [Rd] SEXP i/o, .Call(), and garbage collection.

2007-02-05 Thread K. B. Udaya
Thank you for the prompt and helpful replies. We're embarrassed to report that the problem was far more mundane: a lonely uninitialized integer pointer. On the bright side, we now have a far deeper understanding of SEXP i/o. Rest assured, the C-coding team (that would be me) has be duly spanked

[Rd] SEXP i/o, .Call(), and garbage collection.

2007-02-01 Thread K. B. Udaya
Apologies for any obtuseness in the following. We have been working on Version 2.0 of the randomSurvivalForest CRAN package and we're encountering a perplexing 'memory not mapped' segfault that we believe is "influenced" by GC. We essentially have two R functions, rsf.default(..), and predict.rsf