Mail Archives: djgpp/1997/04/24/04:27:48
Kevin Ashley wrote:
> Usually by corrupting one of the blocks you have malloced (writing off
> the end of it, or writing before the beginning) or, less likely, by
> corrupting malloc's internal tables.
My usual way of doing it is in fact to corrupt the internal tables.
The usual way is to call free with the same pointer twice, or with
something which isn't a malloc'd block (like a static buffer). The
standard free in the library does very little (if any) sanity checking.
Chris
- Raw text -