No idea ? Is that really such a bad idea? :P Emeric
----- Original Message ----- From: "Emeric POUPON" <[email protected]> To: "Tobias Brunner" <[email protected]> Cc: [email protected] Sent: Tuesday, 22 March, 2016 09:55:50 Subject: Re: [strongSwan-dev] malloc check policy Hi, >> 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 [email protected] https://lists.strongswan.org/mailman/listinfo/dev _______________________________________________ Dev mailing list [email protected] https://lists.strongswan.org/mailman/listinfo/dev
