Re: Nasty consequence of fclose followed by ferror

[Garance A Drosihn]

At 11:19 AM +0100 11/23/00, Wolfram Gloger wrote:
>  > However, for the sanity of other people who might run into
> >  this problem, I was wondering if there was some simple and
> >  inexpensive change which could be made to fclose or ferror
> >  which would make debugging this much less painful.
>
> Have you tried running with MALLOC_CHECK_=2 set in the
> environment?  That is relatively inexpensive performance-wise
> and should usually help to find the malloc'ed pointer that
> is `abused'.

Well, I have already fixed the original code.  I might try to
revert to the bad version, and see if the above would have
helped to track down the problem.

Thanks for the hint.
--
Garance Alistair Drosehn            =   address@hidden
Senior Systems Programmer           or  address@hidden
Rensselaer Polytechnic Institute    or  address@hidden