On 2 Jul 2002 at 0:18, colinraybrown wrote:

>
> AAARRRGGGGHHHHH...
> Spent AGES trying to get my memory allocator to stop crashing, I've
> tried all sorts, and re-written much of it to no avail.
> So I tried a memory manager by someone else - Hakim Ferradj of Apex -
> and I get the same flaky behaviour and similar crashes.
Strange behaviour may be caused by memory overwrites, examine this possibility.

> My game works flawlessly with the gcc standard allocator :-|
>
> I'm using c++, so I'm overriding the global new and delete.
>
> The only thing I can think of is that I have to re-compile the
> libraries using my own allocator?? is this the case, might the pre-
> compiled devkit libraries be invoking the original alloc and clashing
> with mine?? - if so does anyone have a link to a tutorial for re-
> building devkit advance
Hmm, I don't think this may be a reason, but you never know. I'm using my own
memory manager with new/delete operators and it works flawlessly (or at least so
it seems
;-). The thing is that my new/delete operators prototypes differ a little bit
from "standard" one because new takes additional arguments (zone). If you want I
may send you
my version, you may test it and see if it still crashes.

--
-Maciej