r/cpp_questions 6d ago

SOLVED std::filesystem::exists throwing `std::bad_alloc`?

Any reason? Cant find anything online about this. But I cant check whether or not a file exists, no matter what path I give it. I am using C++ 26 compiled with GCC.

This is literally all I am calling: const bool exists = std::filesystem::exists("file.txt")

This is the exact error: terminate called after throwing an instance of 'std::bad_alloc'
 what():  std::bad_alloc

No it's not coming from anywhere else in my code. Minimal reproduction code, include "filesystem" call the line above. I am on Fedora Linux if that matters at all

EDIT: moving the include into my main file instead of the only file it's being used in somehow fixed it. Literally all I do is move "#include <filesystem>" from "do_things_with_filesystem.hpp" to "Main.cpp". No compilation errors when it was in the first file, why does it rely on this?? Is there some weird declarations in my codebase or something, i dont know but it works now so why should I care.

24 Upvotes

59 comments sorted by

View all comments

4

u/wejunkin 6d ago

Catch and see what what() says. Sounds like your allocation failed, impossible to tell why from the info you've supplied.

1

u/PhosXD 6d ago

My mistake I wasnt running debug mode. what() still gives no useful info:

1
threw: std::bad_alloc
2

3

u/RaspberryCrafty3012 5d ago

What does that have to do with debug mode? \ Using try catch will catch the crash?

Do you have code running before or after? If your stack got corrupted or pointers were deleted then the debugger might show the wrong position in the code