Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!snorkelwacker.mit.edu!hsdndev!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.unix.questions
Subject: Re: malloc bug ?
Message-ID: <15539@smoke.brl.mil>
Date: 21 Mar 91 01:03:01 GMT
Article-I.D.: smoke.15539
References: <1991Mar20.142604.29925@fmrco>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 10

In article <1991Mar20.142604.29925@fmrco> harold@fmrco (Harold Naparst) writes:
>I have a program which is bombing with a SEGV in a call to malloc.
>I am curious as to what could be causing this.

The usual cause is that the application has corrupted some of the
free-space arena, damaging the bookkeeping information (such as
pointers in a linked list) that the malloc()/free() implementation
relies on to keep track of free space.  Then later, when malloc()
is looking for free space, it gets confused by the damaged
information and falls off the deep end.