From du@@@@dr|@n @end|ng |rom gm@||@com  Thu Apr  7 10:32:37 2022
From: du@@@@dr|@n @end|ng |rom gm@||@com (=?UTF-8?B?QWRyaWFuIER1yJlh?=)
Date: Thu, 7 Apr 2022 11:32:37 +0300
Subject: [Rd] calloc() vs. R_Calloc()
In-Reply-To: <f57301d8-c736-34af-29b1-c59d9458b180@gmail.com>
References: <CAJ=0CtBMDXf4R0DR40whvXS5i8=KUrPRqbZWC-TWWeU2DfzQjw@mail.gmail.com>
 <f57301d8-c736-34af-29b1-c59d9458b180@gmail.com>
Message-ID: <CAJ=0CtAnkUtOqhVVzx7wZUYvRjWZig6HrC700hQUZaRqPE7a_A@mail.gmail.com>

On Thu, 7 Apr 2022 at 10:32, Tomas Kalibera <tomas.kalibera at gmail.com>
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 issue you may run into when switching allocators is
> that you accidentally end up freeing by a different allocator from the
> one used to allocate it. It is common on Windows but can in principle
> happen elsewhere as well.
>
> Also by a slightly different heap layout or different allocator
> implementation you may wake up bugs in the program not seen previously
> (use after free, invalid memory accesses, etc)
>

That is something I do not know yet, since the only information the server
gives is this:
https://builder.r-hub.io/status/original/QCA_3.16.tar.gz-a03b4462b41df37c6284be1d5519e8b3

I'll probably end up debugging the C code, but since the only difference is
using Free() vs free() on exactly the same objects, I suspected a mis-usage
of the R commands.

The same setup passes with no problems on my local MacOS, but the errors
still seem to occur on the Windows setup from r-hub.

Best wishes,
Adrian

	[[alternative HTML version deleted]]



[Rd] calloc() vs. R_Calloc()
=?UTF-8?B?QWRyaWFuIER1yJlh?=