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

From: James Turner (turnerjh@XTN.NET)
Date: 07/16/98

John Woods <JWoodsIII@AOL.COM> writes:

> Nope, no malloc errors. It just crashes. The FIRST call of the CREATE macro
> work fine...but when it gets to that second one, kaboom, no messages, nothing,
> just a Win95 grey message box of death. Any way to limit on Windows95? I don't
> even know how I exceeded it...I'm on a 24 meg ram computer, pentium. I've
> never had any problems, even with AOL, Pueblo, and MSVC++ running.

Sounds like a memory overwrite.  malloc() on linux machines stores
info about the block right before and right after the block itself.
Overwriting this info can cause very odd things to happen, most
usually crashes during a malloc or a free on what seems to be a valid

So... sounds like you've got an overwrite somewhere.

James Turner               UIN: 1102038

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

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