Re: Running app with ARC turned off

[Daniel Santos]

I agree, but my objective is to have ARC disabled to try to reproduce the 
memory allocations that happen in NeXT (that does not have ARC).
Meaning that with ARC disabled I will have to explicitly release objects and 
therefore catching memory allocation bugs that will happen on the NeXTStep 
version  of the code.

Daniel Santos



> On 10 Dec 2024, at 11:29, Andreas Fink <afink@list.fink.org> wrote:
> 
> valgrind should have no issue with ARC at all. In fact it results in objects 
> being released instantly instead of sometimes later so memory issues might 
> show up quicker.
> But as valgrind traces malloc/free calls (or some variants of them) which ARC 
> ultimately use at some point, using ARC or not should not have any effect.
> 
>> On 10 Dec 2024, at 12:07, Daniel Santos <daniel.dlds@gmail.com> wrote:
>> 
>> Hi,
>> 
>> I am developing an application that runs both in NeXTStep and on Linux with 
>> GNUStep.
>> As far as I know GNUStep uses Auto release pools to manage memory and 
>> Automatic Reference Counting.
>> 
>> I want to run the app under valgrind on Linux with ARC turned off because 
>> debugging memory leaks with NeXTStep tool (malloc debug I think that’s what 
>> is called) is much harder and the tool is not as good as valgrind.
>> 
>> Is it possible to turn off ARC in GNUstep ?
>> 
>> Thanks,
>> Regards
>> Daniel Santos
>> 
>> 
>> 
>> 
> 
>