Should we ask the LLVM team if they think it's worth handling the SIGXCPU signal in an alternate way? Since the message they're printing here implies it's a bug in the compiler... or at least, they could print the signal number / signal name in the message log produced. Unless I missed something?
In any case, I agree with the other suggestions re: splitting those functions out into separate files. Another thing worth trying would be to try porting some of these functions from C++ to C -- as far as I can see, you aren't making use of (any?) C++-specific features, beyond the automatic generation of interfaces offered by Rcpp. You could even keep the C++ interfaces auto-generated by Rcpp, but have those call back to separate C functions each defined in separate files, just to keep life simple. Best, Kevin On Tue, Oct 7, 2025 at 10:37 AM Dirk Eddelbuettel <[email protected]> wrote: > > > On 7 October 2025 at 20:07, Ivan Krylov via R-package-devel wrote: > | Clang is programmed to print a message saying "PLEASE submit a bug > | report" when it receives an unexpected fatal signal. Here, the fatal > | signal is SIGXCPU, delivered by the kernel because of the 90-minute > | per-process CPU time limit set for the job [0]. This is not a crash, > | you can see this for yourself using something like > | > | ( ulimit -S -t 2; R -q -s -e 'repeat runif(100)' ) > | > | The bits of information we have are Ttotal=19394.68s [1], the R CMD > | check output [2] saying that R CMD INSTALL tool 94 minutes of real time > | but 323 minutes of userspace plus kernel CPU time, and 00install.log > | saying that the processes being stopped for going over the limit are > | compiling rcpp_bcRel_dec.cpp and rcpp_bc_int.cpp. > > Most excellent work. I suspected this, but was not careful enough: I looked > for SIGKILL so 'today I learned' about SIGXCPU. > > My recommendation ended up being the same though: those files should to be > smaller / simpler. > > Dirk > > -- > dirk.eddelbuettel.com | @eddelbuettel | [email protected] > > ______________________________________________ > [email protected] mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel ______________________________________________ [email protected] mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
