[Date Prev][Date Next]
Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
- From: kurt@OpenLDAP.org
- Date: Thu, 11 Oct 2012 22:52:37 GMT
- Auto-submitted: auto-generated (OpenLDAP-ITS)
On Oct 11, 2012, at 1:44 PM, email@example.com wrote:
> We can describe these and other variables in tests/README.
There's lots of malloc variables one could describe. Better off to simply say that one might want to read the documentation for whatever malloc they are using, and use, if they want, any environmental variables they might want to use. This avoids duplicating detail better left to the malloc documentation.
> Yeah I know, people don't read documentation. The testing
> announcements could mention the file though.
Wrong audience, me thinks, especially if those announcements are posted to openldap-techncial. We don't need openldap users reporting malloc use issues in non-OpenLDAP programs. Use of such variables should be limited to developers.