Boost C++ Libraries: Ticket #7258: boost::filesystem::create_directories(const &path) returns false if the path contains a slash at the end of the string

anonymous — Mon, 03 Sep 2012 12:39:48 GMT

I have same issue!

randydu@… — Mon, 10 Sep 2012 15:15:30 GMT

It also happens on Mac.

The problem is:

path dir("foo/"); dir.parent_path() ==> "foo"; (not "")

hence when create_directories() is called, according to the current implementation (operations.cpp), the parent_path is created ("foo") first, then create_directory("foo/") is called and returns FALSE with an error (BOOST_ERROR_ALREADY_EXISTS).

If the trailing slash is removed:

path dir("foo"); dir.parent_path() ==> ""; (now empty: "")

then everything works perfectly.

So the bug fix is creating a public wrapper of create_directories() to remove trailing slash of input parameter before calling internal create_directories().

Thanks, Randy

anonymous — Wed, 25 Sep 2013 15:21:29 GMT

I have the same issue!! =)

version changed

anonymous — Wed, 02 Oct 2013 10:57:18 GMT

version Boost 1.52.0 → Boost 1.55.0

version changed

gilaldpellaeon@… — Fri, 26 Dec 2014 11:38:59 GMT

version Boost 1.55.0 → Boost 1.57.0

I have the same issue with Boost 1.57.0 (linux).

hadatko — Tue, 17 Feb 2015 13:44:06 GMT

Still problem 1.55.1 you can make this useful with this if(!boost::filesystem::is_directory(dir)) {

boost::filesystem::create_directories(dir); if(!boost::filesystem::is_directory(dir)) {

error code

}

}

status changed; resolution set

Beman Dawes — Wed, 02 Sep 2015 12:26:29 GMT

status new → closed
resolution → fixed

Fixed. Also fixed related issues if path contains dot or dot-dot elements, and added test cases to the test suite.

The fixes have been applied to the develop branch and will be merged to master once sufficient regression tests have cycled.

Thanks,

--Beman

status, version changed; resolution deleted

anonymous — Thu, 08 Oct 2015 19:55:25 GMT

status closed → reopened
version Boost 1.57.0 → Boost 1.59.0
resolution fixed

Hi,

I'm running Boost 1.59 and have found the exact same problem. The bug ISN'T fixed!

Thanks !

# g++ --version

g++ (x86_64-posix-seh-rev0, Built by MinGW-W64 project) 5.2.0 Copyright (C) 2015 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

g++.exe -Wall -fexceptions -g -march=corei7 -std=c++0x -g -IC:\boost_1_59_0 -c C:\temp\c++\main.cpp -o obj\Debug\main.o g++.exe -LC:\boost_1_59_0\stage\lib -o bin\Debug\_recolle_futures.exe obj\Debug\main.o C:\boost_1_59_0\stage\lib\libboost_system-mgw52-mt-1_59.a C:\boost_1_59_0\stage\lib\libboost_filesystem-mgw52-mt-1_59.a C:\boost_1_59_0\stage\lib\libboost_regex-mgw52-mt-1_59.a C:\boost_1_59_0\stage\lib\libboost_program_options-mgw52-mt-1_59.a C:\boost_1_59_0\stage\lib\libboost_date_time-mgw52-mt-1_59.a C:\boost_1_59_0\stage\lib\libboost_iostreams-mgw52-mt-1_59.a

anonymous — Fri, 09 Oct 2015 09:04:02 GMT

By the way, I forgot to mention that I'm running Windows 8.1 pro

milestone changed

Beman Dawes — Fri, 16 Oct 2015 20:04:48 GMT

milestone To Be Determined → Boost 1.60.0

It is fixed in the develop branch for Boost 1.60. Did you test against 1.59 or against the current develop branch of the filesystem repo at https://github.com/boostorg/filesystem?

If it is still failing for you on the current develop branch, please submit a small program that isolates the problem.

Thanks,

--Beman

type, version, component, severity, milestone changed

Smithd407 — Mon, 02 Jan 2017 07:46:04 GMT

type Bugs → Library Submissions
version Boost 1.59.0 → Boost.Build-M3
component filesystem → xpressive
severity Problem → Not Applicable
milestone Boost 1.60.0 → Website 1.X

Thanksamundo for the post.Really thank you! Awesome. ekegdddkdcadbkgf

type, version, component, severity, milestone changed

Kohei Takahashi — Mon, 02 Jan 2017 08:39:12 GMT

type Library Submissions → Bugs
version Boost.Build-M3 → Boost 1.59.0
component xpressive → filesystem
severity Not Applicable → Problem
milestone Website 1.X → To Be Determined

I couldn't undo milestone to 1.60 due to closed.