Path: utzoo!utgpu!water!watmath!clyde!cbosgd!cblpf!eva
From: eva@cblpf.ATT.COM (Eva Martin)
Newsgroups: comp.lang.c
Subject: Re: CALLOC and MALLOC
Message-ID: <1013@cblpf.ATT.COM>
Date: 28 Jan 88 00:18:36 GMT
References: <9991@ccicpg.UUCP>
Reply-To: eva@cblpf.ATT.COM (Eva Martin)
Distribution: na
Organization: AT&T Bell Laboratories - Columbus, Ohio
Lines: 10

In article <9991@ccicpg.UUCP> miket@ccicpg.UUCP (Mike Tracy) writes:
>
>If you do not have a nice debugger, try putting more diagnostics into
>your program (e.g., printf when ever you use malloced memory or when
                                                                 ^^^^
>ever you malloc new memory.)  There is nothing magic about memory allocation.
 ^^^^^^^^^^^^^^^^^^^^^^^^^^

I tried this once.  What happened was I got to find out how quickly the
stack would overflow.  printf is a buffered write.  It calls malloc.