Re: [R-pkg-devel] RFC: C backtraces for R CMD check via just-in-time debugging

On Sun, 3 Mar 2024 19:19:43 -0800 Kevin Ushey wrote: > Would libSegFault be useful here? Glad to know it has been moved to and not just removed altogether after the upstream commit

Re: [R-pkg-devel] RFC: C backtraces for R CMD check via just-in-time debugging

Would libSegFault be useful here? https://lemire.me/blog/2023/05/01/under-linux-libsegfault-and-addr2line-are-underrated/ On Sun, Mar 3, 2024, 5:15 PM Rolf Turner wrote: > On Sun, 3 Mar 2024 11:14:44 +0300 > Ivan Krylov via R-package-devel wrote: > > > Hello, > > > > This may be of interest to

Re: [R-pkg-devel] RFC: C backtraces for R CMD check via just-in-time debugging

On Sun, 3 Mar 2024 11:14:44 +0300 Ivan Krylov via R-package-devel wrote: > Hello, > > This may be of interest to people who run lots of R CMD checks and > have to deal with resulting crashes in compiled code. > Is adding C-level backtraces to R CMD checks worth the effort? Could > it be a goo

[R-pkg-devel] RFC: C backtraces for R CMD check via just-in-time debugging

Hello, This may be of interest to people who run lots of R CMD checks and have to deal with resulting crashes in compiled code. Every now and then, the CRAN checks surface a particularly nasty crash. The R-level traceback stops in the compiled code. It's not obvious where exactly the crash happen