The object really is just built as part of the return statement. i.e. the lines from my prior e-mail exist as-is in the full code, there's just more that actually builds the variables X1-X4 beforehand. So I'm not sure where to debug from the client side. I'm a C/C++ developer, but have no experience with Rcpp internals or the general interface between R and C. I can insert some debug statements on the Rcpp side if you can guide me to where wrap is defined.
What Romain says makes sense to me, despite my lack of expertise in this area.. the really intermittent nature of the problem and the fact that I can't recreate it in a small / fast running example suggests that perhaps this manifests when R happens to garbage collect at an unfortunate time (if I understood correctly). Thanks again. On Wed, May 28, 2014 at 10:12 AM, Dirk Eddelbuettel <[email protected]> wrote: > > On 28 May 2014 at 10:02, John Mous wrote: > | Hmm, unfortunately the GitHub version failed also. > > Darn. > > | The attributes on the failed > | object are a little different though, here's what they look like: > | > | Browse[1]> str(results) > | atomic [1:4] 1 1 2270 0 > | - attr(*, "")= symbol sim > | - attr(*, "value")= promise to NULL > > I am not sure what we can do without a reproducible example. :-/ > The code just got a review / refreshment over the last few months. > > You best bet may the slow and tedious insertion of debug statements to see > when / if the object changes. > > Dirk > > -- > Dirk Eddelbuettel | [email protected] | http://dirk.eddelbuettel.com >
_______________________________________________ Rcpp-devel mailing list [email protected] https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
