Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!ihnp4!zehntel!hplabs!sri-unix!sjh@PURDUE.ARPA From: sjh@PURDUE.ARPA Newsgroups: net.lang.c Subject: Re: C and AWK questions (longish) Message-ID: <12476@sri-arpa.UUCP> Date: Wed, 15-Aug-84 15:09:00 EDT Article-I.D.: sri-arpa.12476 Posted: Wed Aug 15 15:09:00 1984 Date-Received: Sat, 18-Aug-84 01:01:26 EDT Lines: 16 From: Steve Holmes>> We are searching for debugging techniques to track down malloc/realloc >> aborts. Occasionally, our programs get memory faults within the stdio's >> _flsbuf() subroutine. Does anyone have hints on tracking down the types of >> things that would clobber the malloc buffers? > >I believe there are DEBUG defines you can turn on in the malloc source >to compile a debugging version (depending on your OS). WRT the malloc problem: I had the same problem for which the solution was to initialize the pointers to the various blocks of storage to null on the first call. I don't have the code handy but could dig it up if needed. Steve Holmes