On 02/10/2017 02:59, Abhijit Gokaraju wrote: > We have inherited a piece of software which checks for illegal memory > writes due to memory overrun/underrun and writing to released memory. You seem to be interested in debugging dynamically-allocated memory (malloc'ed heap memory). These operations are not handled in gcc, but left up to the libc implementation. For example, if you're using glibc, take a look at man mallopt (especially the env variables) and related functions. http://man7.org/linux/man-pages/man3/mallopt.3.html Tools such as valgrind may prove useful. Regards. > ___________________________________________________________________________ > > This e-mail message is intended for the recipient only and contains information which is > CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this > transmission in error, please inform us by e-mail, phone or fax, and then delete the original > and all copies thereof. > ___________________________________________________________________________ P.S. These footers are silly, especially when writing to a public (and archived) mailing list.
