boost filesystem::path constructor std::length_error

Question

i am trying to iterate over a directory using Boost.Filesystem library.

The problem is that when i try to instantiate a path object, i get an std::length_error with the message "string too long" with strings of any length, even for example "pippo".

I have already tried all of these:

string s = "pippo";

path p(s);
path p(s.begin(), s.end());
path p(s.c_str());
path p("pippo");

I am on windows 7 with boost precompiled version 1.47 for vc++10.

Thank you in advance, Luca

EDIT

this is the boost code executed (path.hpp line 129)

template <class Source>
path(Source const& source,
  typename boost::enable_if<path_traits::is_pathable<
    typename boost::decay<Source>::type> >::type* =0)
{
  path_traits::dispatch(source, m_pathname, codecvt());
}

and the error is thrown from (path_traits.hpp line 174)

template <class U> inline
void dispatch(const std::string& c, U& to, const codecvt_type& cvt)
{
  if (c.size())
  convert(&*c.begin(), &*c.begin() + c.size(), to, cvt);
}

the function that throws is "convert". From the debugger i saw that both

&*c.begin()

and

&*c.begin() + c.size()

are correctly executed

Try running in a debugger and tell us exactly where the error is coming from (file/line). — John Zwinck, Dec 18 '11 at 16:21
Yes this is the exact code. I updated the post with the line that throws. Thank you for help — Luca Piccinelli, Dec 18 '11 at 21:00
Are you using automatic linking to choose the correct boost libraries to link with? This sort of problem can occur if you are using the CRT static libraries and boost is using the CRT in a DLL, or vice versa. — Alan Stokes, Dec 18 '11 at 22:30
I'm not using automatic linking, i manually specify all the libraries i need to link. This is my first experience with vc++, i used to program in C++ only on linux with gnu tools and actually i didn't know about windows CRT and how to check it out if i'm linking it statically. As soon as i can i am going to check it out. — Luca Piccinelli, Dec 19 '11 at 08:20
@Picci any luck doing a custom Boost build? as I investigated further it seems 90% likely that's what you need to do — std''OrgnlDave, Dec 24 '11 at 09:51
Had the same problem, I was mixing debug and release boost dlls. — Adversus, Mar 03 '15 at 09:29

score 1 · Answer 1 · answered Oct 21 '15 at 15:45

A possible error can be found on the library you linked in the project (release instead of a debug one). For example.

Suppose you're using Visual Studio 2010 with "Debug" configuration active. You have to link boost_filesystem-vc100-mt-gd-1_49.dll

boost_filesystem: basename of library

vc100: Visual Studio version (vc100 for VS2010)

mt: multithreading

gd: debug version

1_49: version

Maybe you've linked the library without the "gd".

score 1 · Accepted Answer · answered Dec 23 '11 at 13:50

You mentioned that Boost is pre-compiled for VC++10, but you didn't say which compiler YOU are using. If you are using Visual C++ Express you need to compile it yourself.

But, since I'm about to use boost::filesystem, I thought I'd investigate to learn a bit myself.

Firstly, you should almost never be putting an entire Boost namespace into your plain namespace wherever possible (especially if you are doing so with std!). Posting code like this makes it look like you are "using namespace" too much. If you don't want to type boost::filesystem everywhere, do this:

namespace fs = boost::filesystem;
fs::path p(whatever);

or

using boost::filesystem::path;
using std::string;
string foo("Hello!");
path p(foo);

Including Boost namespaces in your local namespace like you seem to can have disastrous consequences (or work fine, it's the luck of the draw). As you noticed, the function call that kills it is convert() - is there perhaps another convert() somewhere that is superseding it?

Next, you should enable automatic linking (for this library). The official Boost documentation says to use automatic linking. The Boost people are very smart (perhaps too smart - working with the time libraries is a pain...) It works well for Visual Studio 2010.

If that doesn't fix it, your precompiled Boost is using a different CRT (since the convert function appears to be in the Boost library). This can happen for many reasons, for instance, the VS2k10 service pack may be installed on your source/not on yours, etc.

The ultimate solution is to compile Boost yourself. It's very, very easy on Windows: download Boost sources, and extract to any directory. Then open a command prompt (start->run cmd.exe) and do:

cd\
cd "boost root directory"
boostrap
.\b2

Then just wait about 45 minutes on a Core 2 Duo 2.5GHz. It will generate the Boost libraries with the correct CRT. If you still have problems then, then there is something deeper wrong with your build system, such as linking against a static Boost library while using DLL CRT (you should link DLL Boost with DLL CRT).

I compiled manually and used autolinking. Now it works, thank you. By the way, the code lines in my first post are only to exemplify; obviusly i'm using the boost namespace as you suggested. — Luca Piccinelli, Dec 24 '11 at 14:22
@Picci sorry, I keep giving everyone style lessons, haha. I guess it was sort-of relevant here. I'm glad you got it working. I'm deploying on multiple platforms and architectures so it's actually helpful for me to know that it was a CRT issue. Now I know where to look for similar errors if I'm not keeping my binaries up to date across, say, major versions of GCC. — std''OrgnlDave, Dec 24 '11 at 22:46

boost filesystem::path constructor std::length_error

2 Answers2