On Wed, 24 Apr 2002, at 11:47am, [EMAIL PROTECTED] wrote: > I'm interpreting this as an out-of-memory error as a result of too many > file names filling up an array? Is that an accurate interpretation of > this trace?
No, what happened is that the heap management routines detected a corrupion and aborted the program. The great part about memory corruption errors is that where they are caused and where they blow up are often two completely different things. :-( If airplanes were like computers, a light burning out in the bathroom could cause the wing to fall off. -- Ben Scott <[EMAIL PROTECTED]> | The opinions expressed in this message are those of the author and do not | | necessarily represent the views or policy of any other person, entity or | | organization. All information is provided without warranty of any kind. | ***************************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the text 'unsubscribe gnhlug' in the message body. *****************************************************************
