[C++-sig] MSVC 7.1 Multithreaded Dll Memory Leak [long post]

[Paul Grenyer]

Hi

> I am currently running all our unit tests with the static 
> multithreaded runtime. If they pass then we may well switch to that 
> for the time being, but I would prefer to fix the problem and keep 
> using the dll multithreaded runtime.

I'm not sure how relevant to most people this post will be, but for 
those of you that are interested....

All of our C++ unit tests, including those that use the embedded Python 
interpretter ran successfully when linked against the static runtime, 
with one exception (pun intended) where an exception was thrown due to 
an invalid string position. That should be an easy fix and this 
exercise has hopefully thrown up a bug I can fix.

However, all of our boost python extensions (I didn't write the stuff 
and I'm not sure of the right terminology. I mean C++ code wrapped in 
boost python to expose it to python) failed with unknown C++ errors or 
something similar. I suspect this is due to the fact that they are Dlls 
and therefore presumably need the Dll runtime.

Ah! I thought, build everything with the static runtime except the 
boost python extensions. No! The boost pythong extensions use other 
libraries in our system that have already been built with the static 
runtime, so they fail to link.

So, I'm stuck with either having to do two different builds to build 
our whole system (not nice. espcially when you have one large project 
capable of building and running all tests) or try to get the memory 
leak fixed.

Dave, is this memory leak a recognised problem? Is anything being done 
to fix it? As the problem is in function.hpp is it worth posting about 
it to the main boost list?

Thanks!



Regards
Paul

Paul Grenyer
Email: paul at paulgrenyer.co.uk
Web: http://www.paulgrenyer.co.uk

Have you met Aeryn: http://www.paulgrenyer.co.uk/aeryn/?
Version 0.3.0 beta now available for download.