From: Ivan Krylov
Sent: Saturday, 2 March 2024 20:45
To: Murray Efford
Cc: R-package-devel@r-project.org
Subject: Re: [R-pkg-devel] Additional issues: Intel segfault
� Sat, 2 Mar 2024 02:07:47 +
Murray Efford �:
> Gabor suggested
> https://apc01.safelinks.protection.outlook
В Sat, 2 Mar 2024 02:07:47 +
Murray Efford пишет:
> Gabor suggested https://github.com/r-hub/rhub2 and that worked like a
> charm. A check there on the Intel platform found no errors in my
> present version of secrdesign, so I'll resubmit with confidence.
Thank you for letting me know! Havin
mains a
mystery, but not one I need to pursue.
Murray
From: Ivan Krylov
Sent: Friday, 1 March 2024 21:46
To: Murray Efford
Cc: R-package-devel@r-project.org
Subject: Re: [R-pkg-devel] Additional issues: Intel segfault
В Fri, 1 Mar 2024 07:42:01 +
Murray Efford пишет:
> R CMD check sug
В Fri, 1 Mar 2024 07:42:01 +
Murray Efford пишет:
> R CMD check suggests it is most likely in the Examples for
> 'validate', but all code there is wrapped in \dontrun{}.
The crash happens after q('no'), suggesting a corruption in the heap or
in the R memory manager. At least it's a null poin
I am puzzling over an 'Additional issues' error in the CRAN check results for
package secrdesign version 1.8.2 (see
https://CRAN.R-project.org/package=secrdesign, and for an updated version
https://github.com/MurrayEfford/secrdesign) The issue rises with the Intel(R)
oneAPI DPC++/C++ Compiler:
On 1/17/24 09:41, Ivan Krylov via R-package-devel wrote:
В Wed, 17 Jan 2024 10:30:36 +1100
Hugh Parsonage пишет:
I am unable to immediately see where in the test suite this error has
occurred.
Without testthat, you would have gotten a line by line printout of the code,
letting you pinpoint
В Wed, 17 Jan 2024 10:30:36 +1100
Hugh Parsonage пишет:
> I am unable to immediately see where in the test suite this error has
> occurred.
Without testthat, you would have gotten a line by line printout of the code,
letting you pinpoint the (top-level) place of the crash. With
testthat, you wi
On Wed, 17 Jan 2024, Hugh Parsonage wrote:
My package grattan fails the Intel[1] check with
Error: segfault from C stack overflow
I am unable to immediately see where in the test suite this error has
occurred. I seek advice on how to fix this error. The only hunch I
have is that the pack
My package grattan fails the Intel[1] check with
Error: segfault from C stack overflow
I am unable to immediately see where in the test suite this error has
occurred. I seek advice on how to fix this error. The only hunch I
have is that the package uses C code and includes structs with arrays
