Re: [Code] [Stock bug?] write_to_ouput oops. :-)

From: Angus Mezick (angus@EDGIL.CCMAIL.COMPUSERVE.COM)
Date: 07/15/98

Are you getting something about a malloc error in your logs?  if so you are
trying to exceed your memusage and the program is just being shut down on you.
Happens to me all the time.  if you are on UNIX type limit and then limit all

______________________________ Reply Separator _________________________________
Subject: Re:  [Code] [Stock bug?] write_to_ouput oops. :-)
Date:    7/15/98 5:09 PM

John Woods writes:
>    CREATE(t->large_outbuf->text, char, LARGE_BUFSIZE);
>Then I looked at it again, and realized that it was using "char" in there.
>That's not even a variable in the function. Looks like a bug. Anyone tell me
>if I'm right or wrong?

This is confusing, I admit, because CREATE() is a macro and not a
function.  The second argument to create is supposed to be a type so
that the return value of malloc() can be typecast.  If CREATE() is
failing it might indicate you're out of memory.


     | Ensure that you have read the CircleMUD Mailing List FAQ:  |
     | |

This archive was generated by hypermail 2b30 : 12/15/00 PST