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.

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

Or is it more likely that i've produced other code that works only
with the standard new and delete?

any tips for de-bugging this kind of low-level code?

any suggestions much appreciated

cheers,

col.