Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pcl_io] 'boost::filesystem::filesystem_error' what(): boost::filesystem::status: Function not implemented: "XXXX.pcd" #5197

Closed
gaolingminhhh opened this issue Mar 3, 2022 · 4 comments
Labels

Comments

@gaolingminhhh
Copy link

gaolingminhhh commented Mar 3, 2022

I have tried many times to reinstall boost(boost version is 1.76.0) and pcl(1.12.0) ,but the error still here .
When I type pcd_viewer at ubuntu shell,the error occured.

terminate called after throwing an instance of 'boost::filesystem::filesystem_error' what(): boost::filesystem::status: Function not implemented: "kf_output.pcd"

But I have wrote a small program to test boost like this

#define BOOST_NO_CXX11_SCOPED_ENUMS  
#include <boost/filesystem.hpp>  
#undef BOOST_NO_CXX11_SCOPED_ENUMS  
#include <iostream>  
int main(int argc,char** argv)  
{  
    if (boost::filesystem::exists("1.pcd"))  
    {  
        std::cout<<"file exists "<<std::endl;  
    }  
    else  
    {  
        std::cout<<"file not exist!!!!!!!!!"<<std::endl;  
    }  
    return 0;  
}

the output
file not exist!!!!!!!!!

  • OS: [Ubuntu 18.04]
  • Compiler: [GCC 7.5.0]
  • PCL Version [1.12.0]
    -Boost Version[1.76.0]
    2022-03-03 14-04-26屏幕截图
@gaolingminhhh gaolingminhhh added kind: bug Type of issue status: triage Labels incomplete labels Mar 3, 2022
@mvieth
Copy link
Member

mvieth commented Mar 3, 2022

So you just write pcd_viewer and then the path and name of your .pcd file? Are you sure path and name are correct and the file really exists?
Can you run the same command, but with valgrind in front of it?
I am not sure what you intend to do with the program you wrote. You are checking the existence of a file with name "1.pcd", in the same directory as the program. How does that help?
Is it possible that there are non-ASCII characters in the path or name of the file? I don't know how well Boost handles those.

@gaolingminhhh
Copy link
Author

So you just write pcd_viewer and then the path and name of your .pcd file? Are you sure path and name are correct and the file really exists? Can you run the same command, but with valgrind in front of it? I am not sure what you intend to do with the program you wrote. You are checking the existence of a file with name "1.pcd", in the same directory as the program. How does that help? Is it possible that there are non-ASCII characters in the path or name of the file? I don't know how well Boost handles those.

I solved the problem with uninstall boost1.76 and installed boost 1.65.But I don't know the why.

I wrote the program to sure the boost work rightly,I have tracked the pcl::io::loadpcdfile,always corrupted at boost::filesystem::exists().But the small program never corrupt.

@mvieth
Copy link
Member

mvieth commented Mar 9, 2022

I wrote the program to sure the boost work rightly,I have tracked the pcl::io::loadpcdfile,always corrupted at boost::filesystem::exists().But the small program never corrupt.

But you only check "1.pcd" in the small program? Have you checked with the filename you pass to the pcd_viewer? Something like boost::filesystem::exists(argv[1]) and then give the filename on the command line, just like you do with the pcd_viewer?
As I said in my last comment, my best guess would be that there are non-ASCII characters in the path or name of the file, which Boost might not handle correctly.

@mvieth mvieth added module: io and removed status: triage Labels incomplete labels Mar 11, 2022
@mvieth
Copy link
Member

mvieth commented Mar 11, 2022

Closing this issue, since it appears to be solved and since the problem seems to come from Boost, not PCL

@mvieth mvieth closed this as completed Mar 11, 2022
stefled pushed a commit to b-com-software-basis/remaken that referenced this issue Sep 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants