Re: [Boost-users] [filesystem] std::bad_alloc during dll initialization when migrating to filesystem v3

Subject: Re: [Boost-users] [filesystem] std::bad_alloc during dll initialization when migrating to filesystem v3
From: Richard Ulrich (richi_at_[hidden])
Date: 2011-04-15 07:53:25

I can not reproduce the behavior with a toy project containing 3 dlls
that all use boost::filesystem.
It might be some incompatibility with another library. But with
filesystem v2 it works.
So, what should I look for. 
I searched google extensively for  std::bad_alloc during dll
initialization, but found no solution so far.

Rgds
Richard

> Date: Wed, 13 Apr 2011 16:51:41 +0200
> From: Richard Ulrich <richi_at_[hidden]>
> To: boost-users_at_[hidden]
> Subject: [Boost-users] [filesystem] std::bad_alloc during dll
> 	initialization when migrating to filesystem v3
> Message-ID: <1302706301.2665.13.camel_at_one>
> Content-Type: text/plain; charset="us-ascii"
> 
> Hi Guys,
> 
> I'm currently migrating our system consisting of multiple dll's and and
> executable to filesystem v3.
> The first two dll's that use boost::filesystem load ok, but the third
> fails with std::bad_alloc in the locale copy constructor called from
> default_locale during the construction of dot_path.
> 
> I don't know if it's relevant, but we usually work with char while
> filesystem uses wchar_t for BOOST_WINDOWS_API
> 
> Rgds
> Richard