[strongSwan-dev] malloc check policy

Emeric POUPON emeric.poupon at stormshield.eu
Mon Apr 4 17:59:44 CEST 2016

No idea ? Is that really such a bad idea? :P


----- Original Message -----
From: "Emeric POUPON" <emeric.poupon at stormshield.eu>
To: "Tobias Brunner" <tobias at strongswan.org>
Cc: dev at lists.strongswan.org
Sent: Tuesday, 22 March, 2016 09:55:50
Subject: Re: [strongSwan-dev] malloc check policy


>> The question is: since you have done the job to get proper malloc hooks with the
>> leak detective, why not just abort on failure?
> I hope you are not enabling leak detective on your production systems.
> It's quite a hack and has a huge performance impact due to the single lock.

Actually, the leak detective would set the mallocs hooks even if it is unused.
Every real_malloc call would be checked and an abort would be produced on error.
No lock would be involved here, and it has the benefit to catch all the allocations failures for each platform.

Well, "leak_detective" may not be an appropriate name for this new behavior.

What do you think?

Dev mailing list
Dev at lists.strongswan.org

More information about the Dev mailing list