[Rcpp-devel] R CMD check fails on latest RcppEigen using R-devel on Windows

Dear all, In the process of preparing to submit an updated version of a package of mine to CRAN, the R CMD check on my package always failed (i.e., the R instance crashed) when running the 32bit examples involving RcppEigen. On further investigating, it seems that this is already true for the

Re: [Rcpp-devel] R CMD check fails on latest RcppEigen using R-devel on Windows

We heard -- see https://github.com/RcppCore/Rcpp/issues/276 It is at this point unclear if it us, or Rtools but we are aware and this will get addressed. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org ___ Rcpp-devel mailing li

Re: [Rcpp-devel] Rcpp bug (was: [Rd] Notes on building a gcc toolchain for Rtools (but not multilib))

Duncan, The preferred and widely-documented address for Rcpp issues is rcpp-devel where I am forwarding this, I would appreciate keeping follow-up there. On 12 March 2015 at 15:11, Duncan Murdoch wrote: | Jack (and Dirk): | | I see this as well when I recompile Rcpp. | | Dirk: We're seeing th

Re: [Rcpp-devel] Rcpp bug (was: [Rd] Notes on building a gcc toolchain for Rtools (but not multilib))

Just a note that Rf_error is actually not technically allowed in Rcpp (it's a longjmp which bypasses all C++ destructors on the stack). We do it as follows: Rcpp::stop("error message") Which throws an exception which is ultimately caught by our wrapper macro (which then calls Rf_error in a contex

Re: [Rcpp-devel] Rcpp bug (was: [Rd] Notes on building a gcc toolchain for Rtools (but not multilib))

I believe the new toolchain uses SJLJ and not SEH specifically for backwards compatibility. Avi On Thu, Mar 12, 2015 at 4:24 PM, JJ Allaire wrote: > Just a note that Rf_error is actually not technically allowed in Rcpp > (it's a longjmp which bypasses all C++ destructors on the stack). We > do

Re: [Rcpp-devel] Rcpp bug (was: [Rd] Notes on building a gcc toolchain for Rtools (but not multilib))

Just noticed that Rcpp::stop also causes a hang on 64-bit R so the longjmp in the wrapper macro is having the same effect (good to be clear that the destructors being bypassed wasn't the source of the hang/crash) On Thu, Mar 12, 2015 at 4:25 PM, Avraham Adler wrote: > I believe the new toolchain

Re: [Rcpp-devel] Rcpp bug (was: [Rd] Notes on building a gcc toolchain for Rtools (but not multilib))

This is a minimum case to reproduce the crash (no Rcpp involved *however* a C++ destructor being executed seems to be what triggers the crash): #include #include #include extern "C" SEXP foo(SEXP bar) { std::string str; Rf_error("foobar"); return bar; } If I remove the "std::string s

Re: [Rcpp-devel] Rcpp bug (was: [Rd] Notes on building a gcc toolchain for Rtools (but not multilib))

This also does not crash (because the destructor has already run before the longjmp): #include #include #include extern "C" SEXP foo(SEXP bar) { { std::string str; } Rf_error("foobar"); return bar; } Kevin and I are investigating further now. On Thu, Mar 12, 2015 at 4:51 PM,

[Rcpp-devel] V8 crashes on 32bit windows when built with new Rtools

This is probably not exclusively Rcpp problem, but I could use some debugging help from Rcpp experts. When building V8 on windows with the new tool chain, the build succeeds and the package can be loaded, but when trying to use it on i386, it crashes (it works fine on x64). Other packages that lin

Re: [Rcpp-devel] V8 crashes on 32bit windows when built with new Rtools

I had an issue like this in RcppParallel that was solved by rebuilding Rcpp from source using the very latest R-devel and Rtools 3.3. Have you tried that? J.J. On Thu, Mar 12, 2015 at 5:25 PM, Jeroen Ooms wrote: > This is probably not exclusively Rcpp problem, but I could use some > debugging he

Re: [Rcpp-devel] V8 crashes on 32bit windows when built with new Rtools

On Thu, Mar 12, 2015 at 2:40 PM, JJ Allaire wrote: > I had an issue like this in RcppParallel that was solved by rebuilding > Rcpp from source using the very latest R-devel and Rtools 3.3. Have > you tried that? > Yes, that doesn't seem to help. I have a suspicion now. I have seen this behavior

Re: [Rcpp-devel] V8 crashes on 32bit windows when built with new Rtools

On 12/03/2015 5:51 PM, Jeroen Ooms wrote: > On Thu, Mar 12, 2015 at 2:40 PM, JJ Allaire > wrote: > > I had an issue like this in RcppParallel that was solved by rebuilding > Rcpp from source using the very latest R-devel and Rtools 3.3. Have > you tried th

Re: [Rcpp-devel] V8 crashes on 32bit windows when built with new Rtools

Why would posix be enabled for a Windows target? Avi On Thu, Mar 12, 2015 at 6:49 PM, Duncan Murdoch wrote: > On 12/03/2015 5:51 PM, Jeroen Ooms wrote: > > On Thu, Mar 12, 2015 at 2:40 PM, JJ Allaire > > wrote: > > > > I had an issue like this in RcppParallel t

[Rcpp-devel] New Windows toolchain

I've told some of you privately that I'm basically not going to be working on this again before next Wednesday, due to travel. The 3.2.0 release process starts on Monday, and I will be travelling for all but two weeks before the release, so there is very little time left for changes. So here's wh

Re: [Rcpp-devel] New Windows toolchain

Hi Duncan, First off -- a _huge_ thanks for all the time and effort you've put into updating the toolchain on Windows. We understand that, effectively, your (and R-core)'s stake in updating the toolchain on Windows is quite a bit smaller than ours, since C++ support is not a governing priority in