OK, I know nearly nothing about Win32 dev but....
My feeling is a copy constructor bummed out . Are you using a placement new?
Or are you doing a shallow copy when you should be deep? that might explain the range errors in heap_alloc.
Definately a constructor crash though. I've seen this stuff when trying to be to clever with templated constructors doing copies on containers.
BTW, I have some code nearly ready for you Quagmire. Can you send me an email address, as I'm not sure what you'll think of it. And you'll have to check it for win32, which I havent coded on for over 5 years lol.
JP
|