Adrian,
there are many more allocations in your code - for example, you're using
resize() from utils.c which uses malloc/free so it will break since it's using
the wrong allocator. You may need to replace *all* allocations in your project,
not just some.
Cheers,
Simon
> On 8/04/2022, at 6:45
Hello,
Tomas is right, there are many memory operations allocating with malloc
and freeing with R_Free:
line: variables - operation
55: p_pichart - malloc
336: p_pichart - R_Free
236: copy_implicants - malloc
260: copy_implicants - R_Free
240: p_tempic - malloc
262: p_tempic - R_Free
And
On 4/7/22 10:32, Adrian Dușa wrote:
> On Thu, 7 Apr 2022 at 10:32, Tomas Kalibera
> wrote:
>
>
> [...]
>
> And what are the errors you run into? On which platforms, under what
> circumstances, etc? It would be much easier to give advice knowing
> that.
>
> In principle, one
On 4/7/22 08:59, Adrian Dușa wrote:
Dear R devs,
I ran into a C level problem that hopefully is a quick fix to a trained eye.
Not sure if I am able to produce a minimal reproducible example, but
suppose a (test) package passes all the local tests, passes the R CMD check
and also passes the te
