Boost Users :

Date view	Thread view	Subject view	Author view

Subject: Re: [Boost-users] [Boost.Test] workaround for reported memory leaks when using MFC?
From: Gennadiy Rozental (rogeeff_at_[hidden])
Date: 2009-04-14 01:24:01

Next message: Gennadiy Rozental: "Re: [Boost-users] BOOST_CHECK_EQUAL_COLLECTIONS fails to compile when comparing vector<wstring>"
Previous message: David Narvaez: "[Boost-users] Boost::Asio No write handler called after async_write"
Next in thread: gast128: "Re: [Boost-users] [Boost.Test] workaround for reported memory leaks when using MFC?"
Maybe reply: gast128: "Re: [Boost-users] [Boost.Test] workaround for reported memory leaks when using MFC?"

Andrew Durward <andrew.durward <at> cadsoft.com> writes:
> Can anybody suggest a different workaround? The problem effectively renders
> Boost.Test unusable in this configuration when MFC is present.

You can just ignore memory leaks using command line or environment variable

Next message: Gennadiy Rozental: "Re: [Boost-users] BOOST_CHECK_EQUAL_COLLECTIONS fails to compile when comparing vector<wstring>"
Previous message: David Narvaez: "[Boost-users] Boost::Asio No write handler called after async_write"
Next in thread: gast128: "Re: [Boost-users] [Boost.Test] workaround for reported memory leaks when using MFC?"
Maybe reply: gast128: "Re: [Boost-users] [Boost.Test] workaround for reported memory leaks when using MFC?"

Date view	Thread view	Subject view	Author view

Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net