I've had a problem like this before and I also thought that it was due to
some weird magic in OpenMP, but it turned out to be a fence-post error on
my part [1]. Unfortunately, the valgrind output is not as helpful as
something like ASAN. My suggestion would be to go through that section of
the code
Thanks for the suggestion! I tried but to the same effect: no errors.
On Fri, Nov 15, 2019 at 12:01 PM Ivan Krylov wrote:
> On Fri, 15 Nov 2019 10:49:25 -0600
> Marcin Jurek wrote:
>
> > 1) what should I do to reproduce the error?
>
> The following is a quick, unchecked suggestion, but:
>
> `R
On Fri, 15 Nov 2019 10:49:25 -0600
Marcin Jurek wrote:
> 1) what should I do to reproduce the error?
The following is a quick, unchecked suggestion, but:
`R CMD check --use-valgrind` just adds `-d valgrind` to
the command line, while the report you are seeing can only be obtained
with `--leak-
Hello everyone, so my package was rejected from CRAN because of the
following error:
==29416== 640 bytes in 2 blocks are possibly lost in loss record 162 of
2,089
==29416==at 0x4837B65: calloc
(coregrind/m_replacemalloc/vg_replace_malloc.c:762)
==29416==by 0x40118B1: allocate_dtv
(/build/g
